Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dec26ca1e4ba0c8503026fa364ca0eac61808496c79530f89783910de1ab71f

Tx prefix hash: 93c3027006e3ce2f5482beea4e21e98cbdc9c3c73494284efeb1b3c30bd1922e
Tx public key: 9d67ad3d972682e175f89fbdbc4d3ca8bd5bdf7986229b7ce8ed1eb7745f3571
Timestamp: 1713255542 Timestamp [UCT]: 2024-04-16 08:19:02 Age [y:d:h:m:s]: 00:315:04:02:45
Block: 1001621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225304 RingCT/type: yes/0
Extra: 019d67ad3d972682e175f89fbdbc4d3ca8bd5bdf7986229b7ce8ed1eb7745f357102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e7b805b8ed0125b2e4c83dc722c430a60d0f4f48965d9f48e5f7bd3e7e276d 0.600000000000 1462127 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": 1001631, "vin": [ { "gen": { "height": 1001621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e7b805b8ed0125b2e4c83dc722c430a60d0f4f48965d9f48e5f7bd3e7e276d" } } ], "extra": [ 1, 157, 103, 173, 61, 151, 38, 130, 225, 117, 248, 159, 189, 188, 77, 60, 168, 189, 91, 223, 121, 134, 34, 155, 124, 232, 237, 30, 183, 116, 95, 53, 113, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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