Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5246ec1c4180eda43a25b61f267b692b8fab10725ffb0916c9d49c6383989797

Tx prefix hash: d70584613d7932607afa180875dd06c3c63ce4fd15c053d9b7b2bff547809a0c
Tx public key: 69697260908bd2c994b2965a7a17901e4cc9e6a44f6b4b26aa64a766015e9ac8
Timestamp: 1702265663 Timestamp [UCT]: 2023-12-11 03:34:23 Age [y:d:h:m:s]: 01:035:23:34:31
Block: 910526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287079 RingCT/type: yes/0
Extra: 0169697260908bd2c994b2965a7a17901e4cc9e6a44f6b4b26aa64a766015e9ac8021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46193265a2537524c30ab5b8134893da78306da094793e22f01e2e5f3aac756d 0.600000000000 1367687 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": 910536, "vin": [ { "gen": { "height": 910526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46193265a2537524c30ab5b8134893da78306da094793e22f01e2e5f3aac756d" } } ], "extra": [ 1, 105, 105, 114, 96, 144, 139, 210, 201, 148, 178, 150, 90, 122, 23, 144, 30, 76, 201, 230, 164, 79, 107, 75, 38, 170, 100, 167, 102, 1, 94, 154, 200, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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