Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beea97ab5b4e6ec915ae59c1862dbece53c7959f8dfaf40bf4c5ceffd10858d5

Tx prefix hash: e0a40ecf7f1f5cf997fcd874bda0765b176489f40779b737270527a3d0546ce3
Tx public key: c50f91b14df9a210d1e124847fab7d470b7cdfab88ccb15fa07e5947f099f388
Timestamp: 1755041007 Timestamp [UCT]: 2025-08-12 23:23:27 Age [y:d:h:m:s]: 00:100:02:21:57
Block: 1345721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70900 RingCT/type: yes/0
Extra: 01c50f91b14df9a210d1e124847fab7d470b7cdfab88ccb15fa07e5947f099f388021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3db2048afa3a1adab7597a8aa3a4792f0b5432c463a23db556880d6b7d016395 0.600000000000 1833616 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": 1345731, "vin": [ { "gen": { "height": 1345721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db2048afa3a1adab7597a8aa3a4792f0b5432c463a23db556880d6b7d016395" } } ], "extra": [ 1, 197, 15, 145, 177, 77, 249, 162, 16, 209, 225, 36, 132, 127, 171, 125, 71, 11, 124, 223, 171, 136, 204, 177, 95, 160, 126, 89, 71, 240, 153, 243, 136, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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