Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439c9a0fd51a35fa648c70915dc5dc55e8c0117f94e5ba8b11bebd7bbf3de3ad

Tx prefix hash: 2a973f300f17ac9c068bf8d80ebda30237db67d2e2a31c0ad3e933f7b68be876
Tx public key: 1953da2b0b93ca892b7b8ed025f798548718bb78181aaca3546fd71ea2d129ec
Timestamp: 1765482515 Timestamp [UCT]: 2025-12-11 19:48:35 Age [y:d:h:m:s]: 00:028:16:09:22
Block: 1431498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20532 RingCT/type: yes/0
Extra: 011953da2b0b93ca892b7b8ed025f798548718bb78181aaca3546fd71ea2d129ec021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3066c81c23e45c973f74f099b2d08acdafb5923e07d67dbc38431233f427019f 0.600000000000 1920269 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": 1431508, "vin": [ { "gen": { "height": 1431498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3066c81c23e45c973f74f099b2d08acdafb5923e07d67dbc38431233f427019f" } } ], "extra": [ 1, 25, 83, 218, 43, 11, 147, 202, 137, 43, 123, 142, 208, 37, 247, 152, 84, 135, 24, 187, 120, 24, 26, 172, 163, 84, 111, 215, 30, 162, 209, 41, 236, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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