Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63cf8fe7b09001be1211b5109852c8053c4a31ff737a31a1a5d7a361f6617336

Tx prefix hash: e61bf0260375129ce8178f213d83813c8f8a8c6745176ab69570a2939eae0d44
Tx public key: 5cefea096cac4407bb3e3449572df874dd0e8efa806f6e70ef3fc4ae0271a216
Timestamp: 1734491386 Timestamp [UCT]: 2024-12-18 03:09:46 Age [y:d:h:m:s]: 00:022:11:46:05
Block: 1177619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16047 RingCT/type: yes/0
Extra: 015cefea096cac4407bb3e3449572df874dd0e8efa806f6e70ef3fc4ae0271a2160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18fd7fb302734b70708bac1d3a364aec9ac8b0d44af56dbfe0221d59d240bb9c 0.600000000000 1663992 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": 1177629, "vin": [ { "gen": { "height": 1177619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18fd7fb302734b70708bac1d3a364aec9ac8b0d44af56dbfe0221d59d240bb9c" } } ], "extra": [ 1, 92, 239, 234, 9, 108, 172, 68, 7, 187, 62, 52, 73, 87, 45, 248, 116, 221, 14, 142, 250, 128, 111, 110, 112, 239, 63, 196, 174, 2, 113, 162, 22, 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