Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56b538661f02539888f121635c3fa692dcb069d57092fe8ad79b025dc109737

Tx prefix hash: 7462492fed8cb6f08cec886f0671c2501f9cb7a6cc7d3652ca608a24c913d9f1
Tx public key: 4cfe85f70dfedb3842e3650a54d8fefe07ca68853df824fc4fb192dc3c6c88e9
Timestamp: 1709059279 Timestamp [UCT]: 2024-02-27 18:41:19 Age [y:d:h:m:s]: 01:249:09:09:37
Block: 966857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436946 RingCT/type: yes/0
Extra: 014cfe85f70dfedb3842e3650a54d8fefe07ca68853df824fc4fb192dc3c6c88e902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a63d6718fe1473d7625120b6959d34033631ef43f91f156dd18c3f2110b8d2 0.600000000000 1426628 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": 966867, "vin": [ { "gen": { "height": 966857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a63d6718fe1473d7625120b6959d34033631ef43f91f156dd18c3f2110b8d2" } } ], "extra": [ 1, 76, 254, 133, 247, 13, 254, 219, 56, 66, 227, 101, 10, 84, 216, 254, 254, 7, 202, 104, 133, 61, 248, 36, 252, 79, 177, 146, 220, 60, 108, 136, 233, 2, 17, 0, 0, 0, 5, 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