Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06fb14b0ddb5d5a600f01f4c52bc366a11ac97ae6f2c014b86d16a0966a470e4

Tx prefix hash: d6516910d192c1cd38d4f63a0f10771f4686a6575823f093dc8b79310df3bb1d
Tx public key: b1a4b752184ad7b2e061aa11f945d91a3510c4b19fdd452a8a0f2364d347755d
Timestamp: 1708979550 Timestamp [UCT]: 2024-02-26 20:32:30 Age [y:d:h:m:s]: 01:058:18:53:11
Block: 966199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303038 RingCT/type: yes/0
Extra: 01b1a4b752184ad7b2e061aa11f945d91a3510c4b19fdd452a8a0f2364d347755d02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e448ab62d07cf73a22ee00bbf71af77c483ff56c05ee90c1b2cda7d0773084ce 0.600000000000 1425956 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": 966209, "vin": [ { "gen": { "height": 966199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e448ab62d07cf73a22ee00bbf71af77c483ff56c05ee90c1b2cda7d0773084ce" } } ], "extra": [ 1, 177, 164, 183, 82, 24, 74, 215, 178, 224, 97, 170, 17, 249, 69, 217, 26, 53, 16, 196, 177, 159, 221, 69, 42, 138, 15, 35, 100, 211, 71, 117, 93, 2, 17, 0, 0, 0, 9, 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