Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e946bc975db8823f228877d2436b16f75f9238728ac21adc85dcbcee1c1a7b

Tx prefix hash: 7d3c79605b5a2cd7f5373fc4c2f09c7627e3d37a262954b9cdaee17939a0eba7
Tx public key: 4708bc7f5ff1654d8ccbb0c4089ba557241fa4e3d306ead434ff0213975daabf
Timestamp: 1735817895 Timestamp [UCT]: 2025-01-02 11:38:15 Age [y:d:h:m:s]: 00:073:15:10:26
Block: 1188559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52415 RingCT/type: yes/0
Extra: 014708bc7f5ff1654d8ccbb0c4089ba557241fa4e3d306ead434ff0213975daabf021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c288dccdca84469e2bdc1f3e14f99be5a65db7bd5b8e884e4fe9ff5f5217b4 0.600000000000 1675062 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": 1188569, "vin": [ { "gen": { "height": 1188559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c288dccdca84469e2bdc1f3e14f99be5a65db7bd5b8e884e4fe9ff5f5217b4" } } ], "extra": [ 1, 71, 8, 188, 127, 95, 241, 101, 77, 140, 203, 176, 196, 8, 155, 165, 87, 36, 31, 164, 227, 211, 6, 234, 212, 52, 255, 2, 19, 151, 93, 170, 191, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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