Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f692769e430eefc40e97075ed9d5a2b03c398248fc6159c8bd3a183c14c412

Tx prefix hash: a5765053845a1cbbe10867f6009588be22af93dc2e879a56aa7a547d09f66583
Tx public key: a8e4acb6046e07975eac75384725298af688cf5067d0dffcb6a1a8b54adba6d7
Timestamp: 1657101495 Timestamp [UCT]: 2022-07-06 09:58:15 Age [y:d:h:m:s]: 03:117:16:12:10
Block: 537796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863827 RingCT/type: yes/0
Extra: 01a8e4acb6046e07975eac75384725298af688cf5067d0dffcb6a1a8b54adba6d702110000000b4da16a3a000000000000000000

1 output(s) for total of 10.140485594000 dcy

stealth address amount amount idx
00: 0a10ee702c165bdc597cc98cc64dc0602c2d761bfd0cb44d0e2e8f8189cb8d65 10.140485594000 967725 of 0

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": 537806, "vin": [ { "gen": { "height": 537796 } } ], "vout": [ { "amount": 10140485594, "target": { "key": "0a10ee702c165bdc597cc98cc64dc0602c2d761bfd0cb44d0e2e8f8189cb8d65" } } ], "extra": [ 1, 168, 228, 172, 182, 4, 110, 7, 151, 94, 172, 117, 56, 71, 37, 41, 138, 246, 136, 207, 80, 103, 208, 223, 252, 182, 161, 168, 181, 74, 219, 166, 215, 2, 17, 0, 0, 0, 11, 77, 161, 106, 58, 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