Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c7e3cb74c31dc463bf9b18f8a6fed7fb0565846eef69be2c33b6c0c86f19b8

Tx prefix hash: 3f064c033e9a21822bd27dc9e54b119d9413b3d9cbc76b72be78d9540da249de
Tx public key: 391389cc017c9b4c5201ccfa15fafbde4c77f78fe9061a49c45ebd005532939e
Timestamp: 1717305546 Timestamp [UCT]: 2024-06-02 05:19:06 Age [y:d:h:m:s]: 00:151:14:08:08
Block: 1035230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108487 RingCT/type: yes/0
Extra: 01391389cc017c9b4c5201ccfa15fafbde4c77f78fe9061a49c45ebd005532939e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dc9de19ebd7fcc272095832867682e35ba385d96924bc38647eba67c0307b9a 0.600000000000 1503751 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": 1035240, "vin": [ { "gen": { "height": 1035230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dc9de19ebd7fcc272095832867682e35ba385d96924bc38647eba67c0307b9a" } } ], "extra": [ 1, 57, 19, 137, 204, 1, 124, 155, 76, 82, 1, 204, 250, 21, 250, 251, 222, 76, 119, 247, 143, 233, 6, 26, 73, 196, 94, 189, 0, 85, 50, 147, 158, 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