Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3db54a72260a5cc011ed56258bef70c46e51653b399be2d14470e5c451a5c059

Tx prefix hash: ddac097dd342cae60b7a92e7f565fd644fa8dcf52c38c3ce093cad7131338934
Tx public key: e6a2b5f7231944d1045f58e9ae4dc08a756be1e8171195b2cd5d89afcc329fe8
Timestamp: 1726166099 Timestamp [UCT]: 2024-09-12 18:34:59 Age [y:d:h:m:s]: 00:260:10:56:03
Block: 1108671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186028 RingCT/type: yes/0
Extra: 01e6a2b5f7231944d1045f58e9ae4dc08a756be1e8171195b2cd5d89afcc329fe802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc20c20794313d2e1e49b4e3145702b6b825096eb40ecf55a72e875d56fc3891 0.600000000000 1586652 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": 1108681, "vin": [ { "gen": { "height": 1108671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc20c20794313d2e1e49b4e3145702b6b825096eb40ecf55a72e875d56fc3891" } } ], "extra": [ 1, 230, 162, 181, 247, 35, 25, 68, 209, 4, 95, 88, 233, 174, 77, 192, 138, 117, 107, 225, 232, 23, 17, 149, 178, 205, 93, 137, 175, 204, 50, 159, 232, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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