Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047fbdc68bc7d104a766580144e33a7ddf27b7484ae75136d620d09efb0a80d3

Tx prefix hash: 0fb817c6e35e2613acd42cfc5aaf283704bd237b390ec691f949076c0af71b96
Tx public key: 00741adf36ebfc4e92e75fdd9bed95b06ccff9e737d6be5a93c09d11be6b68bb
Timestamp: 1720635331 Timestamp [UCT]: 2024-07-10 18:15:31 Age [y:d:h:m:s]: 01:120:00:40:02
Block: 1062830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344292 RingCT/type: yes/0
Extra: 0100741adf36ebfc4e92e75fdd9bed95b06ccff9e737d6be5a93c09d11be6b68bb021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c43683e17cb45b7d2c56a69c81b4af76ff36fdf67bcad20c1b8a67fa6ecf839 0.600000000000 1533339 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": 1062840, "vin": [ { "gen": { "height": 1062830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c43683e17cb45b7d2c56a69c81b4af76ff36fdf67bcad20c1b8a67fa6ecf839" } } ], "extra": [ 1, 0, 116, 26, 223, 54, 235, 252, 78, 146, 231, 95, 221, 155, 237, 149, 176, 108, 207, 249, 231, 55, 214, 190, 90, 147, 192, 157, 17, 190, 107, 104, 187, 2, 17, 0, 0, 0, 1, 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