Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769307cde6d30adaf8e1d6c67d5bf220e5d87752c83260463419de38ebd857c0

Tx prefix hash: 8a651e14304b3b54c6fdae5bb44e128feecce27a6739a50e12cd375f9dc3a92d
Tx public key: 8be6532787866d249a2b0a42843265fb5b296929cf0c544d2b43afaa83dd63db
Timestamp: 1577192464 Timestamp [UCT]: 2019-12-24 13:01:04 Age [y:d:h:m:s]: 05:006:03:19:48
Block: 30718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154403 RingCT/type: yes/0
Extra: 018be6532787866d249a2b0a42843265fb5b296929cf0c544d2b43afaa83dd63db021100000006d81c26c0000000000000000000

1 output(s) for total of 485.558096326000 dcy

stealth address amount amount idx
00: b65a341dbbbf0792a7d0467b1263c4fe1d30a78574929f9e741e1115873f88c9 485.558096326000 50712 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": 30728, "vin": [ { "gen": { "height": 30718 } } ], "vout": [ { "amount": 485558096326, "target": { "key": "b65a341dbbbf0792a7d0467b1263c4fe1d30a78574929f9e741e1115873f88c9" } } ], "extra": [ 1, 139, 230, 83, 39, 135, 134, 109, 36, 154, 43, 10, 66, 132, 50, 101, 251, 91, 41, 105, 41, 207, 12, 84, 77, 43, 67, 175, 170, 131, 221, 99, 219, 2, 17, 0, 0, 0, 6, 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