Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a5ed7dabadc20660c31a9d0d85db65a12a8e11e9a66adc4253cc7937699039

Tx prefix hash: ccee2ba738ec6781f762bf228bdc03bd0f05aa038fd288dcb2a470e05fc071ac
Tx public key: 2a0eaf5b8ac503005495069feb362bb61b3f9982395e4a25438dfcb192a076a6
Timestamp: 1743164535 Timestamp [UCT]: 2025-03-28 12:22:15 Age [y:d:h:m:s]: 00:046:14:20:02
Block: 1249115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33330 RingCT/type: yes/0
Extra: 012a0eaf5b8ac503005495069feb362bb61b3f9982395e4a25438dfcb192a076a60211000000019ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8a2cb9516e886ef3a4a6086c1034c1c45784c5c6ef5033f712566e92d7d1937 0.600000000000 1736150 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": 1249125, "vin": [ { "gen": { "height": 1249115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8a2cb9516e886ef3a4a6086c1034c1c45784c5c6ef5033f712566e92d7d1937" } } ], "extra": [ 1, 42, 14, 175, 91, 138, 197, 3, 0, 84, 149, 6, 159, 235, 54, 43, 182, 27, 63, 153, 130, 57, 94, 74, 37, 67, 141, 252, 177, 146, 160, 118, 166, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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