Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ca36ec84a6c4d2dded32c4521fd0175b2a89d8b7f42dafcaef47aec52dae50

Tx prefix hash: a8e04b092d952cff3786e45cbfb624d41d7c444e4dc510b0c17f867d90bea91a
Tx public key: 380aeeb658f1cfb2bd1e403bea8b731850c320611f35e84ca6f0337433e02b98
Timestamp: 1763464075 Timestamp [UCT]: 2025-11-18 11:07:55 Age [y:d:h:m:s]: 00:009:18:43:20
Block: 1414770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6998 RingCT/type: yes/0
Extra: 01380aeeb658f1cfb2bd1e403bea8b731850c320611f35e84ca6f0337433e02b98021100000004defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d070d83084628d04a3acfbd9d9e30443d0aad8ebdf8522e96105e112476e718 0.600000000000 1903263 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": 1414780, "vin": [ { "gen": { "height": 1414770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d070d83084628d04a3acfbd9d9e30443d0aad8ebdf8522e96105e112476e718" } } ], "extra": [ 1, 56, 10, 238, 182, 88, 241, 207, 178, 189, 30, 64, 59, 234, 139, 115, 24, 80, 195, 32, 97, 31, 53, 232, 76, 166, 240, 51, 116, 51, 224, 43, 152, 2, 17, 0, 0, 0, 4, 222, 251, 143, 24, 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