Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ff9844e1207ecb715dc527718158596a59180b3df43be7b7e2572c07be9278

Tx prefix hash: ff2191b604e2784beba89150425d20a1a2e07650b1b8ea4be93ee8efb298d9d3
Tx public key: 4e4af0da276e01fa1ea5697a604e29cc0e53dc7b32a1420e56ec3c3d0f4a8867
Timestamp: 1741051999 Timestamp [UCT]: 2025-03-04 01:33:19 Age [y:d:h:m:s]: 00:309:13:25:34
Block: 1231619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219073 RingCT/type: yes/0
Extra: 014e4af0da276e01fa1ea5697a604e29cc0e53dc7b32a1420e56ec3c3d0f4a8867021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dbe0106859f547008824fc68b9584fe3dba2e9d25e3350032c840520430b3ec 0.600000000000 1718528 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": 1231629, "vin": [ { "gen": { "height": 1231619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dbe0106859f547008824fc68b9584fe3dba2e9d25e3350032c840520430b3ec" } } ], "extra": [ 1, 78, 74, 240, 218, 39, 110, 1, 250, 30, 165, 105, 122, 96, 78, 41, 204, 14, 83, 220, 123, 50, 161, 66, 14, 86, 236, 60, 61, 15, 74, 136, 103, 2, 17, 0, 0, 0, 4, 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