Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b590d7c152d2657348280ac950b924fc9b269870457f6524fa280ac4299d4a2

Tx prefix hash: 06cd23790c98b882b72b0b9825970ef633aa27b1cf647146fc5f646e4d6b1001
Tx public key: 0a93a97a00cf4fdc835e58f301da87a1c86da6f96b9e669d5db9e1bdabcb9fed
Timestamp: 1720530263 Timestamp [UCT]: 2024-07-09 13:04:23 Age [y:d:h:m:s]: 01:125:05:37:15
Block: 1061961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348024 RingCT/type: yes/0
Extra: 010a93a97a00cf4fdc835e58f301da87a1c86da6f96b9e669d5db9e1bdabcb9fed02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501f5e3d82797ffe7a8072e20abd0a1600adacf1cc8f96d2ee2c944bcc60b9e7 0.600000000000 1532460 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": 1061971, "vin": [ { "gen": { "height": 1061961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501f5e3d82797ffe7a8072e20abd0a1600adacf1cc8f96d2ee2c944bcc60b9e7" } } ], "extra": [ 1, 10, 147, 169, 122, 0, 207, 79, 220, 131, 94, 88, 243, 1, 218, 135, 161, 200, 109, 166, 249, 107, 158, 102, 157, 93, 185, 225, 189, 171, 203, 159, 237, 2, 17, 0, 0, 0, 15, 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