Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cbbebb15f39283c8d6b256f7d1993a617a6317d87dd3a723dba0cf182ade2c9

Tx prefix hash: 1af85511c436e2586d8f4b5ae22b640f0801e71aa5aedf08208ef27529af36d5
Tx public key: 801c8ef631762b67ef45fcd02987ec5ab6680a84c2ac6b18361c0ee2e9f9d277
Timestamp: 1718804048 Timestamp [UCT]: 2024-06-19 13:34:08 Age [y:d:h:m:s]: 00:302:08:29:47
Block: 1047645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216051 RingCT/type: yes/0
Extra: 01801c8ef631762b67ef45fcd02987ec5ab6680a84c2ac6b18361c0ee2e9f9d2770211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48d6bf7f6f71c882c802c081cede90ed79fc46b01a8af537419ec89aca9b0edc 0.600000000000 1517520 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": 1047655, "vin": [ { "gen": { "height": 1047645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48d6bf7f6f71c882c802c081cede90ed79fc46b01a8af537419ec89aca9b0edc" } } ], "extra": [ 1, 128, 28, 142, 246, 49, 118, 43, 103, 239, 69, 252, 208, 41, 135, 236, 90, 182, 104, 10, 132, 194, 172, 107, 24, 54, 28, 14, 226, 233, 249, 210, 119, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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