Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf33bdce88977e50ea64482417548f693d56a603d48639d66abe212d796ac14c

Tx prefix hash: 929fd0ebee1447b4daf26a5c3360f2703427b9d26575fd4a170c9b6f569c28a9
Tx public key: 4cbef8ed0a64d2a12876fb3a3e8fe3417388373f0cd1effc3504e6214f617875
Timestamp: 1705739907 Timestamp [UCT]: 2024-01-20 08:38:27 Age [y:d:h:m:s]: 01:121:18:18:55
Block: 939297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348174 RingCT/type: yes/0
Extra: 014cbef8ed0a64d2a12876fb3a3e8fe3417388373f0cd1effc3504e6214f61787502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83d1e8d5c7717f49a59916a86056bdb4c848353738579d9f2761ab527f19ab41 0.600000000000 1397389 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": 939307, "vin": [ { "gen": { "height": 939297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83d1e8d5c7717f49a59916a86056bdb4c848353738579d9f2761ab527f19ab41" } } ], "extra": [ 1, 76, 190, 248, 237, 10, 100, 210, 161, 40, 118, 251, 58, 62, 143, 227, 65, 115, 136, 55, 63, 12, 209, 239, 252, 53, 4, 230, 33, 79, 97, 120, 117, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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