Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6317cbed38c8a0375f41396649257aacc2c894cf0dd119b4b9902e189d930c77

Tx prefix hash: 5b4da3d8788f42ae0b87a8741fd2f199ec99d550eab4578de5f8fa0f1e695162
Tx public key: 72a01e02c09fe3897d629c0479e31fdd2ceab559bfac6c5dabfa046b6e7bd1f7
Timestamp: 1703812981 Timestamp [UCT]: 2023-12-29 01:23:01 Age [y:d:h:m:s]: 01:139:22:48:34
Block: 923347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361166 RingCT/type: yes/0
Extra: 0172a01e02c09fe3897d629c0479e31fdd2ceab559bfac6c5dabfa046b6e7bd1f7021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 895d4f516630e332a24fe5c2a34b8b55f0675f8e279195223e06241e87a35c32 0.600000000000 1381079 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": 923357, "vin": [ { "gen": { "height": 923347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "895d4f516630e332a24fe5c2a34b8b55f0675f8e279195223e06241e87a35c32" } } ], "extra": [ 1, 114, 160, 30, 2, 192, 159, 227, 137, 125, 98, 156, 4, 121, 227, 31, 221, 44, 234, 181, 89, 191, 172, 108, 93, 171, 250, 4, 107, 110, 123, 209, 247, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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