Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e39b9d9470ee5849b598fea93e0459d8dcf5f58cf3d351cb659f82bd14d266

Tx prefix hash: 125e51ab1f8c8de8e6062ee5bf6aee29b16fb13effd730477d7f71c485290c89
Tx public key: decef7d9d34ffdecd904e7257e13d61dd537ca6b51558e05225ca5845afc3c8f
Timestamp: 1719563796 Timestamp [UCT]: 2024-06-28 08:36:36 Age [y:d:h:m:s]: 01:132:18:33:01
Block: 1053936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353437 RingCT/type: yes/0
Extra: 01decef7d9d34ffdecd904e7257e13d61dd537ca6b51558e05225ca5845afc3c8f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 979fb6ad221b1f0d67cc098dd006a1f44d060b5d8da5a5df7ccea119a49c2fb1 0.600000000000 1524291 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": 1053946, "vin": [ { "gen": { "height": 1053936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979fb6ad221b1f0d67cc098dd006a1f44d060b5d8da5a5df7ccea119a49c2fb1" } } ], "extra": [ 1, 222, 206, 247, 217, 211, 79, 253, 236, 217, 4, 231, 37, 126, 19, 214, 29, 213, 55, 202, 107, 81, 85, 142, 5, 34, 92, 165, 132, 90, 252, 60, 143, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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