Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12c98fca417f24067f45985ee5badd94598faa3a35f7808c57e12bc61865ebd

Tx prefix hash: 3a81c459d9489f95c5484b31e867c54698100b6f115c607f01498dce802b51c1
Tx public key: 7bcd5e3abcb04dd27c0a591fca713e67df4b822e083c0240248e55354c6f4212
Timestamp: 1741457025 Timestamp [UCT]: 2025-03-08 18:03:45 Age [y:d:h:m:s]: 00:324:00:03:01
Block: 1234989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229218 RingCT/type: yes/0
Extra: 017bcd5e3abcb04dd27c0a591fca713e67df4b822e083c0240248e55354c6f42120211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8da22ec9f87564f8651dff1b38a9d63c4e31bfc64c6d9cae4494f4abdadebbd 0.600000000000 1721924 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": 1234999, "vin": [ { "gen": { "height": 1234989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8da22ec9f87564f8651dff1b38a9d63c4e31bfc64c6d9cae4494f4abdadebbd" } } ], "extra": [ 1, 123, 205, 94, 58, 188, 176, 77, 210, 124, 10, 89, 31, 202, 113, 62, 103, 223, 75, 130, 46, 8, 60, 2, 64, 36, 142, 85, 53, 76, 111, 66, 18, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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