Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330f30d3a9ff47c23e0ebb11e95655c3117faafe29275b11fce9b364eddb4d7e

Tx prefix hash: ab9d619974de2fae3389f63ec331c61399bdeb8c108fae05f39c1fe47eafd23f
Tx public key: 0df84d467c74f3e67e3cea72f30d5abc081d89eac5d8644ddf74a0a0c70887aa
Timestamp: 1695332624 Timestamp [UCT]: 2023-09-21 21:43:44 Age [y:d:h:m:s]: 01:208:10:06:49
Block: 853239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410041 RingCT/type: yes/0
Extra: 010df84d467c74f3e67e3cea72f30d5abc081d89eac5d8644ddf74a0a0c70887aa021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.913829237000 dcy

stealth address amount amount idx
00: 3f77fda175c3f4e2487ebfbc252c4af07be3c4e1ea38275fc9adb41c89ad6a1f 0.913829237000 1307131 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": 853249, "vin": [ { "gen": { "height": 853239 } } ], "vout": [ { "amount": 913829237, "target": { "key": "3f77fda175c3f4e2487ebfbc252c4af07be3c4e1ea38275fc9adb41c89ad6a1f" } } ], "extra": [ 1, 13, 248, 77, 70, 124, 116, 243, 230, 126, 60, 234, 114, 243, 13, 90, 188, 8, 29, 137, 234, 197, 216, 100, 77, 223, 116, 160, 160, 199, 8, 135, 170, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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