Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95427c95af045f7104949fede4544253252a50bae8e5c2024bd80864fcac063

Tx prefix hash: dbe460a26fc6b3ae7c89d3ce2d20993ea7b3e99d495fa96701f77f6634745960
Tx public key: 902a66f2dda744cf1b6d0501e54b5e122efa66ed76cad545a5c3c4991bd2b02d
Timestamp: 1700641188 Timestamp [UCT]: 2023-11-22 08:19:48 Age [y:d:h:m:s]: 01:140:00:14:28
Block: 897051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361249 RingCT/type: yes/0
Extra: 01902a66f2dda744cf1b6d0501e54b5e122efa66ed76cad545a5c3c4991bd2b02d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.654180570000 dcy

stealth address amount amount idx
00: 53c7cbf2c8a79eeb249de7681750c05932f3b94b63552c601e2c49f203eb5941 0.654180570000 1353406 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": 897061, "vin": [ { "gen": { "height": 897051 } } ], "vout": [ { "amount": 654180570, "target": { "key": "53c7cbf2c8a79eeb249de7681750c05932f3b94b63552c601e2c49f203eb5941" } } ], "extra": [ 1, 144, 42, 102, 242, 221, 167, 68, 207, 27, 109, 5, 1, 229, 75, 94, 18, 46, 250, 102, 237, 118, 202, 213, 69, 165, 195, 196, 153, 27, 210, 176, 45, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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