Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e89216b3b9fd5b07add0c2c9bddf8e3d49b6a5b75288d7101fefd88f3f264d7

Tx prefix hash: 3cb96c6ff7e89263a2dcb1430198ecefb225bc5d5cc11adc8458e2049ea355b2
Tx public key: 314e3f2995ad0432236ce81b327d1c9124ccd26cdf86c0fc72c0928d507364cb
Timestamp: 1711986050 Timestamp [UCT]: 2024-04-01 15:40:50 Age [y:d:h:m:s]: 00:355:01:37:45
Block: 991076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253902 RingCT/type: yes/0
Extra: 01314e3f2995ad0432236ce81b327d1c9124ccd26cdf86c0fc72c0928d507364cb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30ac14d0e53b15ec9ac3a5d3eae80d5810263bda25c09e72f6a6c81cf8cf14c3 0.600000000000 1451410 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": 991086, "vin": [ { "gen": { "height": 991076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30ac14d0e53b15ec9ac3a5d3eae80d5810263bda25c09e72f6a6c81cf8cf14c3" } } ], "extra": [ 1, 49, 78, 63, 41, 149, 173, 4, 50, 35, 108, 232, 27, 50, 125, 28, 145, 36, 204, 210, 108, 223, 134, 192, 252, 114, 192, 146, 141, 80, 115, 100, 203, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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