Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489e90821db0a1236d2401f30297e739f1c28d556da4793f11cdb74b27295d6e

Tx prefix hash: 240c5c44109a8305932574359588ec8cd12ef4f0578a320f56b86a1412627437
Tx public key: fe1927d3bc9fd0ffb0d4b54b5ff60c34603b120025856c70f3fb56e9eb8dc49c
Timestamp: 1721140978 Timestamp [UCT]: 2024-07-16 14:42:58 Age [y:d:h:m:s]: 00:290:23:23:46
Block: 1067026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207890 RingCT/type: yes/0
Extra: 01fe1927d3bc9fd0ffb0d4b54b5ff60c34603b120025856c70f3fb56e9eb8dc49c021100000004e914dd15000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: 0b037bd34db7059143ed413b66abb0d8eeffa30b97eed4cc348e160683e6e9b6 0.615580000000 1537727 of 0

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": 1067036, "vin": [ { "gen": { "height": 1067026 } } ], "vout": [ { "amount": 615580000, "target": { "key": "0b037bd34db7059143ed413b66abb0d8eeffa30b97eed4cc348e160683e6e9b6" } } ], "extra": [ 1, 254, 25, 39, 211, 188, 159, 208, 255, 176, 212, 181, 75, 95, 246, 12, 52, 96, 59, 18, 0, 37, 133, 108, 112, 243, 251, 86, 233, 235, 141, 196, 156, 2, 17, 0, 0, 0, 4, 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