Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f783a61194ff4a63e8627bda91ff6ead6ef44eb8349e1502ea7d3f8b97b9c82

Tx prefix hash: 47c26ee6573b6bd7db1375c3697ce0591e58056a8ed7e47d49d73e97c3d5f6fc
Tx public key: 19d276514ce5779e60170d9e708d9bf2282277fb15f2bd9c276d4386eae160db
Timestamp: 1710981610 Timestamp [UCT]: 2024-03-21 00:40:10 Age [y:d:h:m:s]: 01:003:19:16:47
Block: 982812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263658 RingCT/type: yes/0
Extra: 0119d276514ce5779e60170d9e708d9bf2282277fb15f2bd9c276d4386eae160db0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7255725f39b6dc22ce5177b7c8c28f3abb6e71a2f0add370fc343fdd68d37fed 0.600000000000 1442923 of 15

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": 982822, "vin": [ { "gen": { "height": 982812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7255725f39b6dc22ce5177b7c8c28f3abb6e71a2f0add370fc343fdd68d37fed" } } ], "extra": [ 1, 25, 210, 118, 81, 76, 229, 119, 158, 96, 23, 13, 158, 112, 141, 155, 242, 40, 34, 119, 251, 21, 242, 189, 156, 39, 109, 67, 134, 234, 225, 96, 219, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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