Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2bc46bd7b64e12eca9c9f520af17cf3ae59f850ca2288d1fcc81230b7b6829

Tx prefix hash: dce016aa2f4b0737d0324fbcd6e931c8689d8854e8c87cc99038c7bf3ee1158d
Tx public key: 8113523ae31f68a4d1a622f7d9a1f35be87d24e93878319c566397af13cb6e5f
Timestamp: 1575906925 Timestamp [UCT]: 2019-12-09 15:55:25 Age [y:d:h:m:s]: 05:021:03:36:08
Block: 24180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161033 RingCT/type: yes/0
Extra: 018113523ae31f68a4d1a622f7d9a1f35be87d24e93878319c566397af13cb6e5f021100000005d81c26c0000000000000000000

1 output(s) for total of 510.366891645000 dcy

stealth address amount amount idx
00: aabff4b5a0c2cc3bfb5eb1a55e06d7b8713f11bc21a4763e6b6c6ea4440bcb96 510.366891645000 39521 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": 24190, "vin": [ { "gen": { "height": 24180 } } ], "vout": [ { "amount": 510366891645, "target": { "key": "aabff4b5a0c2cc3bfb5eb1a55e06d7b8713f11bc21a4763e6b6c6ea4440bcb96" } } ], "extra": [ 1, 129, 19, 82, 58, 227, 31, 104, 164, 209, 166, 34, 247, 217, 161, 243, 91, 232, 125, 36, 233, 56, 120, 49, 156, 86, 99, 151, 175, 19, 203, 110, 95, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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