Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5165ad1ac2066fac4e1b0b94920bbd2d5ef6f459e7ee47e12e36df4a53ba05f6

Tx prefix hash: 39f5cd0db920c78478e50e2dbe67eba67ba786d02fa4ace9f06d8db81b277093
Tx public key: b41bbc9a8613cbdefbcb4b1f01636688ee04bd6dc3e552dc91e786e84a68d9f7
Timestamp: 1733632877 Timestamp [UCT]: 2024-12-08 04:41:17 Age [y:d:h:m:s]: 00:125:12:03:37
Block: 1170477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89496 RingCT/type: yes/0
Extra: 01b41bbc9a8613cbdefbcb4b1f01636688ee04bd6dc3e552dc91e786e84a68d9f7021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44209a145f917416c0a57c7e6ebe051e53bf75bc07350ad6a3b235d2bc46e56 0.600000000000 1656208 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": 1170487, "vin": [ { "gen": { "height": 1170477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44209a145f917416c0a57c7e6ebe051e53bf75bc07350ad6a3b235d2bc46e56" } } ], "extra": [ 1, 180, 27, 188, 154, 134, 19, 203, 222, 251, 203, 75, 31, 1, 99, 102, 136, 238, 4, 189, 109, 195, 229, 82, 220, 145, 231, 134, 232, 74, 104, 217, 247, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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