Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03461b218392f48ef168516c5ef683ea613b7da6c6c6d49624670e9fc6a648c3

Tx prefix hash: ec0dbd2a6e8ab4267619dc3a5d1139c9cc7586d6821c9a35b39ad712ddfa571a
Tx public key: 0a19755e1ed21ff65c629fb5e98985368ca13bf5d5215ae203c74f5fbdf11c75
Timestamp: 1709347049 Timestamp [UCT]: 2024-03-02 02:37:29 Age [y:d:h:m:s]: 01:278:19:50:48
Block: 969242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458030 RingCT/type: yes/0
Extra: 010a19755e1ed21ff65c629fb5e98985368ca13bf5d5215ae203c74f5fbdf11c750211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60566a38c602cd9063c02ea573fd61996c8feb1c6f1b1aa9e031d61049aeda64 0.600000000000 1429071 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": 969252, "vin": [ { "gen": { "height": 969242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60566a38c602cd9063c02ea573fd61996c8feb1c6f1b1aa9e031d61049aeda64" } } ], "extra": [ 1, 10, 25, 117, 94, 30, 210, 31, 246, 92, 98, 159, 181, 233, 137, 133, 54, 140, 161, 59, 245, 213, 33, 90, 226, 3, 199, 79, 95, 189, 241, 28, 117, 2, 17, 0, 0, 0, 3, 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