Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06be45a4c59c5ed88472e3df90807109ac35b77c667cc0dae76a085634145254

Tx prefix hash: 28479f994b2d4026802e413c9646b16eb9e91485bb7f745621c0db8f7defc42e
Tx public key: f46898f8252ae8bdd5baa7fe251b3f9b0d387627fce354eefec76ae85fa938c4
Timestamp: 1761870040 Timestamp [UCT]: 2025-10-31 00:20:40 Age [y:d:h:m:s]: 00:065:09:05:12
Block: 1401570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46815 RingCT/type: yes/0
Extra: 01f46898f8252ae8bdd5baa7fe251b3f9b0d387627fce354eefec76ae85fa938c402110000000ddf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd481d6e43ffccb14526e28abae24bfd1bcbd63b710cf80498d6d9044b2cc3d0 0.600000000000 1889889 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": 1401580, "vin": [ { "gen": { "height": 1401570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd481d6e43ffccb14526e28abae24bfd1bcbd63b710cf80498d6d9044b2cc3d0" } } ], "extra": [ 1, 244, 104, 152, 248, 37, 42, 232, 189, 213, 186, 167, 254, 37, 27, 63, 155, 13, 56, 118, 39, 252, 227, 84, 238, 254, 199, 106, 232, 95, 169, 56, 196, 2, 17, 0, 0, 0, 13, 223, 90, 36, 122, 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