Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a792683c226386a64e3d54bf86179237a6c6a2ecc4144fbfdde1d158457dd305

Tx prefix hash: 2b077916be6434336438e782d0721f42249fa0bb6f8ef0a7090be68414cc1673
Tx public key: f0f4ab2a913e68748e195e4870d12c3f281acfd3fcf7ceebd441a9db2fa1dfed
Timestamp: 1728107410 Timestamp [UCT]: 2024-10-05 05:50:10 Age [y:d:h:m:s]: 00:209:14:50:34
Block: 1124765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149621 RingCT/type: yes/0
Extra: 01f0f4ab2a913e68748e195e4870d12c3f281acfd3fcf7ceebd441a9db2fa1dfed02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7476d5a27332a89ac23828a85bfb51b523220e67919f1b5bda1edf726c4fd9bd 0.600000000000 1607432 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": 1124775, "vin": [ { "gen": { "height": 1124765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7476d5a27332a89ac23828a85bfb51b523220e67919f1b5bda1edf726c4fd9bd" } } ], "extra": [ 1, 240, 244, 171, 42, 145, 62, 104, 116, 142, 25, 94, 72, 112, 209, 44, 63, 40, 26, 207, 211, 252, 247, 206, 235, 212, 65, 169, 219, 47, 161, 223, 237, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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