Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf1b5d8e9c4cc77ef9cc0984e17a1e8b47b1d94eae97190b68894f945f85c5af

Tx prefix hash: b2446eb3cf8962f88965eb5180abcffc41365f9bd3372f7173bbd99b285e4d94
Tx public key: fd90a90f0df1c68717013c23f3ddbef34833a8359060369d69e62d78f3aa2614
Timestamp: 1706437864 Timestamp [UCT]: 2024-01-28 10:31:04 Age [y:d:h:m:s]: 01:070:21:28:48
Block: 945095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311750 RingCT/type: yes/0
Extra: 01fd90a90f0df1c68717013c23f3ddbef34833a8359060369d69e62d78f3aa26140211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 692f7a8e101f094e23cba925f4ddfc9b88f407717d0528789853efa023871006 0.600000000000 1403405 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": 945105, "vin": [ { "gen": { "height": 945095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "692f7a8e101f094e23cba925f4ddfc9b88f407717d0528789853efa023871006" } } ], "extra": [ 1, 253, 144, 169, 15, 13, 241, 198, 135, 23, 1, 60, 35, 243, 221, 190, 243, 72, 51, 168, 53, 144, 96, 54, 157, 105, 230, 45, 120, 243, 170, 38, 20, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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