Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8add61a33ae4e1e2d1c8c06593477d00b20fc5da27d6fd8bf1c94d194631adba

Tx prefix hash: e67fc895f7be20e2b0b6bfe080867f804064c19b205d387ee00452db5574a98a
Tx public key: 864b10c297af8b406a0dbdcfa7dceb7e32329172b3c4b8563ae84548e04a71d2
Timestamp: 1712569860 Timestamp [UCT]: 2024-04-08 09:51:00 Age [y:d:h:m:s]: 01:212:01:00:43
Block: 995929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410219 RingCT/type: yes/0
Extra: 01864b10c297af8b406a0dbdcfa7dceb7e32329172b3c4b8563ae84548e04a71d202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8011a9d677b2001972fa0c3395e81f14053e1aae05bcd09896218641c54e856 0.600000000000 1456345 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": 995939, "vin": [ { "gen": { "height": 995929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8011a9d677b2001972fa0c3395e81f14053e1aae05bcd09896218641c54e856" } } ], "extra": [ 1, 134, 75, 16, 194, 151, 175, 139, 64, 106, 13, 189, 207, 167, 220, 235, 126, 50, 50, 145, 114, 179, 196, 184, 86, 58, 232, 69, 72, 224, 74, 113, 210, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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