Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0edc5bbfc7e143511194fb602fd0e31e89b46da5af77e1d722dab9f8bdc3e7c

Tx prefix hash: e431b5db1787cd007728e6cf3609ba305a953292eed3cf07a1b9718b3f39d7a5
Tx public key: 7f4591af80fad3249d59074afc1def10f9fefc55c7eab4c331524d154a1ea1b3
Timestamp: 1703537188 Timestamp [UCT]: 2023-12-25 20:46:28 Age [y:d:h:m:s]: 01:123:20:23:36
Block: 921070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349649 RingCT/type: yes/0
Extra: 017f4591af80fad3249d59074afc1def10f9fefc55c7eab4c331524d154a1ea1b302110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7cf12321e558deab9d4068eac1186127c1844764fe183ab5314333b6ae7ae3 0.600000000000 1378754 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": 921080, "vin": [ { "gen": { "height": 921070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7cf12321e558deab9d4068eac1186127c1844764fe183ab5314333b6ae7ae3" } } ], "extra": [ 1, 127, 69, 145, 175, 128, 250, 211, 36, 157, 89, 7, 74, 252, 29, 239, 16, 249, 254, 252, 85, 199, 234, 180, 195, 49, 82, 77, 21, 74, 30, 161, 179, 2, 17, 0, 0, 0, 8, 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