Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29f92ece72c9fafa5c52dc70a196694e73e00b109dbbfe65219c8358d05b55ba

Tx prefix hash: 1358185458e7b0f0f3c852b5d496fa8cc8887341e0bb2a340b5798371fbb7478
Tx public key: e0ef33c428edc3c0e0acc7af6a3bda99efe5bbf60c125d990e9e965bf0f3b970
Timestamp: 1736599990 Timestamp [UCT]: 2025-01-11 12:53:10 Age [y:d:h:m:s]: 00:345:07:11:26
Block: 1195029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244348 RingCT/type: yes/0
Extra: 01e0ef33c428edc3c0e0acc7af6a3bda99efe5bbf60c125d990e9e965bf0f3b9700211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 665d7f883ae07989a1e669af69e128c3879aa5fd26942d87605c9cbde4f11247 0.600000000000 1681614 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": 1195039, "vin": [ { "gen": { "height": 1195029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "665d7f883ae07989a1e669af69e128c3879aa5fd26942d87605c9cbde4f11247" } } ], "extra": [ 1, 224, 239, 51, 196, 40, 237, 195, 192, 224, 172, 199, 175, 106, 59, 218, 153, 239, 229, 187, 246, 12, 18, 93, 153, 14, 158, 150, 91, 240, 243, 185, 112, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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