Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf980be551e9cbc8e1a0521c5bb999fd6f7fcf63ba8485a98cff2cab37c3f8c

Tx prefix hash: 75bf96a033f4377a95669bfdce505fa59298f153f7801e16da912dc88b3d25c0
Tx public key: 372d632d6cd4689b76bd18906ee67e094315f2c375b1e73f02b1c7b08ec63cd5
Timestamp: 1724313556 Timestamp [UCT]: 2024-08-22 07:59:16 Age [y:d:h:m:s]: 00:205:01:08:10
Block: 1093337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146402 RingCT/type: yes/0
Extra: 01372d632d6cd4689b76bd18906ee67e094315f2c375b1e73f02b1c7b08ec63cd5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01c0f421edfdc1842207917a96e8a33bd2bc7ead3845dcd684347fd1aa4735f9 0.600000000000 1568260 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": 1093347, "vin": [ { "gen": { "height": 1093337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01c0f421edfdc1842207917a96e8a33bd2bc7ead3845dcd684347fd1aa4735f9" } } ], "extra": [ 1, 55, 45, 99, 45, 108, 212, 104, 155, 118, 189, 24, 144, 110, 230, 126, 9, 67, 21, 242, 195, 117, 177, 231, 63, 2, 177, 199, 176, 142, 198, 60, 213, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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