Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 871b5b0f8f41e87a8582860c3e590f910023873b5f407474795e80a611217b55

Tx prefix hash: 356cf1dd0e4881811a3ade445eba365b8b1da51f12f65cfa2bf4a3775709abf2
Tx public key: d014d25e47d069aeeba7c36f8cb0aea03b879c8cc0612034e01ccaaf77e0cf3c
Timestamp: 1740828102 Timestamp [UCT]: 2025-03-01 11:21:42 Age [y:d:h:m:s]: 00:257:23:24:40
Block: 1229763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182130 RingCT/type: yes/0
Extra: 01d014d25e47d069aeeba7c36f8cb0aea03b879c8cc0612034e01ccaaf77e0cf3c021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50681670aee98440d2119cee7f2a15b8c9734c1ef26412adf509257f7e117e8c 0.600000000000 1716652 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": 1229773, "vin": [ { "gen": { "height": 1229763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50681670aee98440d2119cee7f2a15b8c9734c1ef26412adf509257f7e117e8c" } } ], "extra": [ 1, 208, 20, 210, 94, 71, 208, 105, 174, 235, 167, 195, 111, 140, 176, 174, 160, 59, 135, 156, 140, 192, 97, 32, 52, 224, 28, 202, 175, 119, 224, 207, 60, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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