Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794de0678d1f49e6edd8af9aa977cb7435444a8101f677daae76938ff573e37e

Tx prefix hash: 68cc943fd5beac3da522bb680d9f1d7873510db69aefabbaf74cd5bf1d3711cd
Tx public key: 3efe6ddcdc8df55867da4a9b199d3df98c149fb182f54236a4ec44eeaa622e9f
Timestamp: 1751551469 Timestamp [UCT]: 2025-07-03 14:04:29 Age [y:d:h:m:s]: 00:139:00:08:05
Block: 1317983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97588 RingCT/type: yes/0
Extra: 013efe6ddcdc8df55867da4a9b199d3df98c149fb182f54236a4ec44eeaa622e9f02110000001243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f22b035ff6910b5fb2fd5e738f902189f342be1fe475e3a5008d52dc87d4ee4 0.600000000000 1805654 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": 1317993, "vin": [ { "gen": { "height": 1317983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f22b035ff6910b5fb2fd5e738f902189f342be1fe475e3a5008d52dc87d4ee4" } } ], "extra": [ 1, 62, 254, 109, 220, 220, 141, 245, 88, 103, 218, 74, 155, 25, 157, 61, 249, 140, 20, 159, 177, 130, 245, 66, 54, 164, 236, 68, 238, 170, 98, 46, 159, 2, 17, 0, 0, 0, 18, 67, 132, 109, 102, 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