Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766b4185c9ed64ae20883be2a16abfb668c8a7ac95481b09a185a9ce1cd9f0e3

Tx prefix hash: 49b9c92fa625fdf37d6bceb7afdd1fe47d8f1e0dfe080c6106a4ecf433a78a29
Tx public key: b4ab68398d1ffd226b78ba5da3867e8348878e830eb272de7fa1262ab2ee23ae
Timestamp: 1731890886 Timestamp [UCT]: 2024-11-18 00:48:06 Age [y:d:h:m:s]: 00:006:04:59:26
Block: 1156048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4435 RingCT/type: yes/0
Extra: 01b4ab68398d1ffd226b78ba5da3867e8348878e830eb272de7fa1262ab2ee23ae021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a90ae1bfe6d13953a6129d34609ca35520fbeb9dbe543a57701b021dc0c75c4b 0.600000000000 1641667 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": 1156058, "vin": [ { "gen": { "height": 1156048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90ae1bfe6d13953a6129d34609ca35520fbeb9dbe543a57701b021dc0c75c4b" } } ], "extra": [ 1, 180, 171, 104, 57, 141, 31, 253, 34, 107, 120, 186, 93, 163, 134, 126, 131, 72, 135, 142, 131, 14, 178, 114, 222, 127, 161, 38, 42, 178, 238, 35, 174, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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