Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec444a051b1252276f862bd5ffd6ae0adee76370bdb5481b5931e8e1dc7664a

Tx prefix hash: c1fcfd5ca572d5bf209243488b77749c7225e158692f2898425cffd9b485e6e3
Tx public key: 4476e794a31c032bd5ed7a15f60b7bb9e02ee2e593ae59b9a430a27071a49299
Timestamp: 1733245247 Timestamp [UCT]: 2024-12-03 17:00:47 Age [y:d:h:m:s]: 00:197:06:49:15
Block: 1167270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140706 RingCT/type: yes/0
Extra: 014476e794a31c032bd5ed7a15f60b7bb9e02ee2e593ae59b9a430a27071a492990211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493232d979f675ed3580ea7e0a5333089c222d77143cb2a84f47e025b80623d3 0.600000000000 1652965 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": 1167280, "vin": [ { "gen": { "height": 1167270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493232d979f675ed3580ea7e0a5333089c222d77143cb2a84f47e025b80623d3" } } ], "extra": [ 1, 68, 118, 231, 148, 163, 28, 3, 43, 213, 237, 122, 21, 246, 11, 123, 185, 224, 46, 226, 229, 147, 174, 89, 185, 164, 48, 162, 112, 113, 164, 146, 153, 2, 17, 0, 0, 0, 8, 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