Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9ab5d8b250fa3d1f052d80acefe3d5670820d8e24dfd3c36bc18f6d609de2d3c

Tx prefix hash: 770e0c9922a4be56f1065ed9a0798e1c3356102352d3e0bb02205ea7d027fd3a
Tx public key: 8a911c17061ebc1bd633feff259c5f0303e8b0649799b0c6caaaf33d0d45052a
Timestamp: 1587141315 Timestamp [UCT]: 2020-04-17 16:35:15 Age [y:d:h:m:s]: 05:023:18:05:33
Block: 93315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186503 RingCT/type: yes/0
Extra: 018a911c17061ebc1bd633feff259c5f0303e8b0649799b0c6caaaf33d0d45052a02110000000186362411000000000000000000

1 output(s) for total of 301.168425710000 dcy

stealth address amount amount idx
00: fc78a06713f0fa00e77cb8c84666548ae9e9a81e434735ddc8b326b5d5f1e131 301.168425710000 166279 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 93325, "vin": [ { "gen": { "height": 93315 } } ], "vout": [ { "amount": 301168425710, "target": { "key": "fc78a06713f0fa00e77cb8c84666548ae9e9a81e434735ddc8b326b5d5f1e131" } } ], "extra": [ 1, 138, 145, 28, 23, 6, 30, 188, 27, 214, 51, 254, 255, 37, 156, 95, 3, 3, 232, 176, 100, 151, 153, 176, 198, 202, 170, 243, 61, 13, 69, 5, 42, 2, 17, 0, 0, 0, 1, 134, 54, 36, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8