Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4df97bef117dbaeffa2fc0589b32ce2dc1a3498d22e627fcb15bc1204d81edc

Tx prefix hash: 75b4dab1055782c5fcd619ec69b25e3fae280e95da47809fbc4e702dbc5710e0
Tx public key: e7f2415a4f3cafde546b2c1274c0cfe8a94b568d32513128962e9e831a111ea4
Timestamp: 1727179272 Timestamp [UCT]: 2024-09-24 12:01:12 Age [y:d:h:m:s]: 00:109:07:49:16
Block: 1117077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78154 RingCT/type: yes/0
Extra: 01e7f2415a4f3cafde546b2c1274c0cfe8a94b568d32513128962e9e831a111ea402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc6759b97c9388a68e98f23dbeb7dc526109856c6ef289b4cd31d72caf70f39a 0.600000000000 1597784 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": 1117087, "vin": [ { "gen": { "height": 1117077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc6759b97c9388a68e98f23dbeb7dc526109856c6ef289b4cd31d72caf70f39a" } } ], "extra": [ 1, 231, 242, 65, 90, 79, 60, 175, 222, 84, 107, 44, 18, 116, 192, 207, 232, 169, 75, 86, 141, 50, 81, 49, 40, 150, 46, 158, 131, 26, 17, 30, 164, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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