Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ee9fbe70c79e245264e148d575ae5fcc4c6b4c293d8c5c7441004a82b4bef3

Tx prefix hash: 078ada8f079a00c8cfc8ab3d3c8f3b02c75638736059a55b4b639f955a2a6be2
Tx public key: 6cb14bef87606b8c01aa221bbd7af5476b83ee50edf38e82feccf6c020d648fc
Timestamp: 1764038316 Timestamp [UCT]: 2025-11-25 02:38:36 Age [y:d:h:m:s]: 00:002:06:13:42
Block: 1419526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1625 RingCT/type: yes/0
Extra: 016cb14bef87606b8c01aa221bbd7af5476b83ee50edf38e82feccf6c020d648fc021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 199f917026b025399640a9bb159701f2eafc56f10451dda0b25c1215e396d113 0.600000000000 1908063 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": 1419536, "vin": [ { "gen": { "height": 1419526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "199f917026b025399640a9bb159701f2eafc56f10451dda0b25c1215e396d113" } } ], "extra": [ 1, 108, 177, 75, 239, 135, 96, 107, 140, 1, 170, 34, 27, 189, 122, 245, 71, 107, 131, 238, 80, 237, 243, 142, 130, 254, 204, 246, 192, 32, 214, 72, 252, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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