Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d4d496c617838eee205a9b51c1d1f00c43cec8c84b6cf0576f3ea181657a3e

Tx prefix hash: 6dd7ec4b20fadf92d186a9a4e14657a31c68663368dacae4429d78e0e254f1ef
Tx public key: 76e6c1177060bb644b8093e050de7e359ab331225be447f4ee615406f5dae880
Timestamp: 1721351174 Timestamp [UCT]: 2024-07-19 01:06:14 Age [y:d:h:m:s]: 00:275:07:25:09
Block: 1068767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196678 RingCT/type: yes/0
Extra: 0176e6c1177060bb644b8093e050de7e359ab331225be447f4ee615406f5dae88002110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 246c6fce44d8def1ab3922d8b205245cb9c4afd1e2268ac2a9c02acf1fdb06e1 0.600000000000 1539928 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": 1068777, "vin": [ { "gen": { "height": 1068767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "246c6fce44d8def1ab3922d8b205245cb9c4afd1e2268ac2a9c02acf1fdb06e1" } } ], "extra": [ 1, 118, 230, 193, 23, 112, 96, 187, 100, 75, 128, 147, 224, 80, 222, 126, 53, 154, 179, 49, 34, 91, 228, 71, 244, 238, 97, 84, 6, 245, 218, 232, 128, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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