Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4cf3c981ef06688e845e28a4dc5f3c48b3019655b5d6d7a1c3b720c36b3a0f

Tx prefix hash: 7d984057743add260326c463472522d323c29da89f346254b23b323a8f2da5c1
Tx public key: 866b36d4ed011cfb74580a9a5456fb6aa4258b004e509ad9b0a5631f8c95a661
Timestamp: 1705500046 Timestamp [UCT]: 2024-01-17 14:00:46 Age [y:d:h:m:s]: 01:078:12:53:19
Block: 937323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317225 RingCT/type: yes/0
Extra: 01866b36d4ed011cfb74580a9a5456fb6aa4258b004e509ad9b0a5631f8c95a66102110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f8f5bb7b726ebae681fca91d00d077a08e396c0c6e215af2a912001faf6603 0.600000000000 1395373 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": 937333, "vin": [ { "gen": { "height": 937323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f8f5bb7b726ebae681fca91d00d077a08e396c0c6e215af2a912001faf6603" } } ], "extra": [ 1, 134, 107, 54, 212, 237, 1, 28, 251, 116, 88, 10, 154, 84, 86, 251, 106, 164, 37, 139, 0, 78, 80, 154, 217, 176, 165, 99, 31, 140, 149, 166, 97, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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