Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553747a00562ff0ce9652c8b575b212d79118b076f5696fb3041069c92a1557c

Tx prefix hash: 765b342f4db2b6f5f8c65343f2706b288eea01ea5cefb8bc33a86b10782363a6
Tx public key: 0cdeabd6fc4c9aec4f1e281b45d206bd814f55cc4252349ac729eb12ecd645a2
Timestamp: 1717579499 Timestamp [UCT]: 2024-06-05 09:24:59 Age [y:d:h:m:s]: 00:344:23:08:16
Block: 1037496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246550 RingCT/type: yes/0
Extra: 010cdeabd6fc4c9aec4f1e281b45d206bd814f55cc4252349ac729eb12ecd645a202110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d349dce1f77544e617e3d68bbf8d4de60131365a59ceb6f98f2a0cb7b15fe713 0.600000000000 1506041 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": 1037506, "vin": [ { "gen": { "height": 1037496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d349dce1f77544e617e3d68bbf8d4de60131365a59ceb6f98f2a0cb7b15fe713" } } ], "extra": [ 1, 12, 222, 171, 214, 252, 76, 154, 236, 79, 30, 40, 27, 69, 210, 6, 189, 129, 79, 85, 204, 66, 82, 52, 154, 199, 41, 235, 18, 236, 214, 69, 162, 2, 17, 0, 0, 0, 16, 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