Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64997f359cc37f06789761bc2e63044af27f4e88ae6c2b6c81947aeef07f90d2

Tx prefix hash: a6d7bd69d49575bd10b67d2156dd5f8c8afc1c62b2e26cd11bbc3d5cfd659584
Tx public key: 3865e5f0d7b49f943b93ad212013b0fbe3517bdb22f05a459c7a3132b6585f96
Timestamp: 1724585926 Timestamp [UCT]: 2024-08-25 11:38:46 Age [y:d:h:m:s]: 00:296:14:34:04
Block: 1095576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211777 RingCT/type: yes/0
Extra: 013865e5f0d7b49f943b93ad212013b0fbe3517bdb22f05a459c7a3132b6585f9602110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c358e847c7353dd0c9d02b6cda30dd3504313c050bfa428ecf39db9d312b6df 0.600000000000 1570757 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": 1095586, "vin": [ { "gen": { "height": 1095576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c358e847c7353dd0c9d02b6cda30dd3504313c050bfa428ecf39db9d312b6df" } } ], "extra": [ 1, 56, 101, 229, 240, 215, 180, 159, 148, 59, 147, 173, 33, 32, 19, 176, 251, 227, 81, 123, 219, 34, 240, 90, 69, 156, 122, 49, 50, 182, 88, 95, 150, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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