Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9c36ab292fc93a89a9ca1c12a3d401f51433e40a018d369e78922f214b364ab

Tx prefix hash: fc82307161b7c70b3456384f2a058a67668f465a39deeef3df6d75f445d5364c
Tx public key: 16a3b5724d2b56b07cd38c756e347dcf24aeab2c21ec539e9a58a438ade50625
Timestamp: 1731075946 Timestamp [UCT]: 2024-11-08 14:25:46 Age [y:d:h:m:s]: 00:015:17:00:22
Block: 1149297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11238 RingCT/type: yes/0
Extra: 0116a3b5724d2b56b07cd38c756e347dcf24aeab2c21ec539e9a58a438ade506250211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dcf2a83bd1ece79f598c5407aea760cacfc8a0f4596ae05a9f67ff7353d2c9e 0.600000000000 1634344 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": 1149307, "vin": [ { "gen": { "height": 1149297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dcf2a83bd1ece79f598c5407aea760cacfc8a0f4596ae05a9f67ff7353d2c9e" } } ], "extra": [ 1, 22, 163, 181, 114, 77, 43, 86, 176, 124, 211, 140, 117, 110, 52, 125, 207, 36, 174, 171, 44, 33, 236, 83, 158, 154, 88, 164, 56, 173, 229, 6, 37, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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