Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245a7c4c729f9757cd84a8fc4d1287a6bb4bd9989f18a20e0f430d8c8ba0d838

Tx prefix hash: d5327f13e5f5a5aedaf555ad8a4852c4dc8cdc1090543f8e4b6488476452fa85
Tx public key: d3e986dba84c1265cf4821e27fbbcf30744a8783bb49e7ac7c32bb94c430add1
Timestamp: 1711736100 Timestamp [UCT]: 2024-03-29 18:15:00 Age [y:d:h:m:s]: 01:046:22:38:23
Block: 989066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294516 RingCT/type: yes/0
Extra: 01d3e986dba84c1265cf4821e27fbbcf30744a8783bb49e7ac7c32bb94c430add10211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 336c6d2b7e34efc687c34dfd68b28f96474073c5c9572db49e2aeb8d0f88bf2c 0.600000000000 1449361 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": 989076, "vin": [ { "gen": { "height": 989066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "336c6d2b7e34efc687c34dfd68b28f96474073c5c9572db49e2aeb8d0f88bf2c" } } ], "extra": [ 1, 211, 233, 134, 219, 168, 76, 18, 101, 207, 72, 33, 226, 127, 187, 207, 48, 116, 74, 135, 131, 187, 73, 231, 172, 124, 50, 187, 148, 196, 48, 173, 209, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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