Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb7f890cccdadabddd080897f423241ab2df550d3e7aecd3e7c6a84d4686dabe

Tx prefix hash: e67d7c2155b4bd02929ab51a66d3125addb84c6d75fb35554d82c1896cd2a452
Tx public key: 9eafb2e7e9df2b79fc788b1be6d808f2996b71af9a71ca40013288b7bbdc7610
Timestamp: 1764870569 Timestamp [UCT]: 2025-12-04 17:49:29 Age [y:d:h:m:s]: 00:026:10:41:25
Block: 1426434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18924 RingCT/type: yes/0
Extra: 019eafb2e7e9df2b79fc788b1be6d808f2996b71af9a71ca40013288b7bbdc761002110000000bd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cabeb7b71ffd730002455c231b9e2a467787863807eaa6bbb1d2133172821c4 0.600000000000 1915125 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": 1426444, "vin": [ { "gen": { "height": 1426434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cabeb7b71ffd730002455c231b9e2a467787863807eaa6bbb1d2133172821c4" } } ], "extra": [ 1, 158, 175, 178, 231, 233, 223, 43, 121, 252, 120, 139, 27, 230, 216, 8, 242, 153, 107, 113, 175, 154, 113, 202, 64, 1, 50, 136, 183, 187, 220, 118, 16, 2, 17, 0, 0, 0, 11, 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