Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88de8c9229c3f0120f62584604235b8c570fd50a1dc765b98ab4c35902da6410

Tx prefix hash: b4a4ce42bf92cdd602607e357b885ae522035e4b7993415381162c0120703067
Tx public key: ef4def399f1ca9890dc7a38e4f6f1144211dcafaeea534c3d2d3d475c7592c30
Timestamp: 1704309700 Timestamp [UCT]: 2024-01-03 19:21:40 Age [y:d:h:m:s]: 01:163:13:03:12
Block: 927481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377933 RingCT/type: yes/0
Extra: 01ef4def399f1ca9890dc7a38e4f6f1144211dcafaeea534c3d2d3d475c7592c3002110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab0f4301cc71d960dacc33a81a331e56ce261dc365da84fefe04c58c02adafe4 0.600000000000 1385317 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": 927491, "vin": [ { "gen": { "height": 927481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab0f4301cc71d960dacc33a81a331e56ce261dc365da84fefe04c58c02adafe4" } } ], "extra": [ 1, 239, 77, 239, 57, 159, 28, 169, 137, 13, 199, 163, 142, 79, 111, 17, 68, 33, 29, 202, 250, 238, 165, 52, 195, 210, 211, 212, 117, 199, 89, 44, 48, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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