Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 818736569e331e9f8536e45e47cf96a4b8185e69991b228e16e8b04b2392da87

Tx prefix hash: 0a265c21c514092de1fc098c10478d392c5858ad9a818f67265b569bae1ab15a
Tx public key: 48d9be48d9bf87b29870c9c33552fdb61674771a7df5649961a0a7c139ce7de9
Timestamp: 1713831555 Timestamp [UCT]: 2024-04-23 00:19:15 Age [y:d:h:m:s]: 00:308:05:43:10
Block: 1006412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220324 RingCT/type: yes/0
Extra: 0148d9be48d9bf87b29870c9c33552fdb61674771a7df5649961a0a7c139ce7de902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0df4fcdce5a343b1fe4baaa57417f4de0981b7a403d47e31f526694d830c954 0.600000000000 1467438 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": 1006422, "vin": [ { "gen": { "height": 1006412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0df4fcdce5a343b1fe4baaa57417f4de0981b7a403d47e31f526694d830c954" } } ], "extra": [ 1, 72, 217, 190, 72, 217, 191, 135, 178, 152, 112, 201, 195, 53, 82, 253, 182, 22, 116, 119, 26, 125, 245, 100, 153, 97, 160, 167, 193, 57, 206, 125, 233, 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