Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09a75c9c2559646d7c073062e2034378c84f5435a9df557af183ee482e43f043

Tx prefix hash: 50ef73148dcc2eee5293ee0edf6e93d5fa2988a0b27cad24da5cca6ec4d0ae95
Tx public key: 0ebe2d7970dc916bfba825aa3b5dba09d7d3d699d1d13b27c80d98159fe79928
Timestamp: 1730988863 Timestamp [UCT]: 2024-11-07 14:14:23 Age [y:d:h:m:s]: 00:074:20:39:32
Block: 1148571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53516 RingCT/type: yes/0
Extra: 010ebe2d7970dc916bfba825aa3b5dba09d7d3d699d1d13b27c80d98159fe799280211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163583ff2445d2de02c08a6f9b0ad747a1a23107deb6ef95a9b709737288afe0 0.600000000000 1633448 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": 1148581, "vin": [ { "gen": { "height": 1148571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163583ff2445d2de02c08a6f9b0ad747a1a23107deb6ef95a9b709737288afe0" } } ], "extra": [ 1, 14, 190, 45, 121, 112, 220, 145, 107, 251, 168, 37, 170, 59, 93, 186, 9, 215, 211, 214, 153, 209, 209, 59, 39, 200, 13, 152, 21, 159, 231, 153, 40, 2, 17, 0, 0, 0, 2, 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