Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b8395ca0ed8c3298a707523752217d1ce2d0100502b8c1417d3f5281d524050

Tx prefix hash: 5a7cf44f5dc03914d5581f36bdf852e4895c89a196edb060eb2d2ee5bc31439b
Tx public key: 528ff712384fd3c0158e8caae6b2aa9d3bdafb70059ce12236c8bbf86a01c601
Timestamp: 1710468701 Timestamp [UCT]: 2024-03-15 02:11:41 Age [y:d:h:m:s]: 01:003:05:39:15
Block: 978553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263279 RingCT/type: yes/0
Extra: 01528ff712384fd3c0158e8caae6b2aa9d3bdafb70059ce12236c8bbf86a01c60102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775f4dd06f6041651a194b647d63bab923e0a097b0854d0d8696307c67b41594 0.600000000000 1438580 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": 978563, "vin": [ { "gen": { "height": 978553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775f4dd06f6041651a194b647d63bab923e0a097b0854d0d8696307c67b41594" } } ], "extra": [ 1, 82, 143, 247, 18, 56, 79, 211, 192, 21, 142, 140, 170, 230, 178, 170, 157, 59, 218, 251, 112, 5, 156, 225, 34, 54, 200, 187, 248, 106, 1, 198, 1, 2, 17, 0, 0, 0, 3, 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