Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e67cd7b321a3cc7aad9317a3e1b293c14d9f0d201a168aad971413eb5df4c438

Tx prefix hash: 8c96ab79977c1b483435eb4aeecdccb6dc4a2532dda8c6f1a178e635707db9bd
Tx public key: fa7a8c3d0f86a613396306da7b3dddc3b6bf41ee2f82613da998771e14c445b3
Timestamp: 1750171297 Timestamp [UCT]: 2025-06-17 14:41:37 Age [y:d:h:m:s]: 00:203:21:11:51
Block: 1307010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143584 RingCT/type: yes/0
Extra: 01fa7a8c3d0f86a613396306da7b3dddc3b6bf41ee2f82613da998771e14c445b302110000000d43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa5461d3b35f646de851b68d3f7ad5000016ccddc59acdc8b6193cac9eb7cd41 0.600000000000 1794619 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": 1307020, "vin": [ { "gen": { "height": 1307010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa5461d3b35f646de851b68d3f7ad5000016ccddc59acdc8b6193cac9eb7cd41" } } ], "extra": [ 1, 250, 122, 140, 61, 15, 134, 166, 19, 57, 99, 6, 218, 123, 61, 221, 195, 182, 191, 65, 238, 47, 130, 97, 61, 169, 152, 119, 30, 20, 196, 69, 179, 2, 17, 0, 0, 0, 13, 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