Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa3eab6cf72eba6bbec18b3aecf5f01d4380593eb754159955d4cb7bc8d9205

Tx prefix hash: 3dd1912955d38ad9f91f4725cb2f6636fa41bc5a817d8fc08d1717188dcd113a
Tx public key: d11cb298084398e902dc4f793248e45260d58c0f057ba5e6ce713db7cb2bd07e
Timestamp: 1716047626 Timestamp [UCT]: 2024-05-18 15:53:46 Age [y:d:h:m:s]: 01:174:04:48:41
Block: 1024788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383101 RingCT/type: yes/0
Extra: 01d11cb298084398e902dc4f793248e45260d58c0f057ba5e6ce713db7cb2bd07e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ee650983c3e09ee57f83a02d4851d82bb933f5eb1a23ee36c0fd1f53037381 0.600000000000 1490809 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": 1024798, "vin": [ { "gen": { "height": 1024788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ee650983c3e09ee57f83a02d4851d82bb933f5eb1a23ee36c0fd1f53037381" } } ], "extra": [ 1, 209, 28, 178, 152, 8, 67, 152, 233, 2, 220, 79, 121, 50, 72, 228, 82, 96, 213, 140, 15, 5, 123, 165, 230, 206, 113, 61, 183, 203, 43, 208, 126, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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