Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f870501fc6d9742c80b3e930c8e423c8a1d2eebd5a99ca9b5a30d9b90c662d

Tx prefix hash: 6c7de0c033df9c2fa2edc515e7cbcd36629292d3ab7aae19f8ddae5189bb765c
Tx public key: 496f7462e85cd4afce0a83a84131e684ab7e1f3158573a719d3db53bb5dc10c1
Timestamp: 1711512811 Timestamp [UCT]: 2024-03-27 04:13:31 Age [y:d:h:m:s]: 01:028:02:03:21
Block: 987216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281032 RingCT/type: yes/0
Extra: 01496f7462e85cd4afce0a83a84131e684ab7e1f3158573a719d3db53bb5dc10c102110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6361d9a9ba80d36eb7bcb36a05b9e0f08b24c669f119d42ffa6ff8ca5b91f717 0.600000000000 1447457 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": 987226, "vin": [ { "gen": { "height": 987216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6361d9a9ba80d36eb7bcb36a05b9e0f08b24c669f119d42ffa6ff8ca5b91f717" } } ], "extra": [ 1, 73, 111, 116, 98, 232, 92, 212, 175, 206, 10, 131, 168, 65, 49, 230, 132, 171, 126, 31, 49, 88, 87, 58, 113, 157, 61, 181, 59, 181, 220, 16, 193, 2, 17, 0, 0, 0, 6, 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