Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e13756d1f15cc7a1d53075a6fb2b0de801b9dab689e3b3153a57812db5711b88

Tx prefix hash: 0273c127d7139510ee3ea95f54f84ba28aadbd63c2113aee5c1947670491746f
Tx public key: f92dddcaec70b8ee501a82baf2d28b9e9632af7ef6aecf85f0debff2e56279e8
Timestamp: 1577137726 Timestamp [UCT]: 2019-12-23 21:48:46 Age [y:d:h:m:s]: 05:029:01:31:51
Block: 30132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170893 RingCT/type: yes/0
Extra: 01f92dddcaec70b8ee501a82baf2d28b9e9632af7ef6aecf85f0debff2e56279e80211000000084943cd9f000000000000000000

1 output(s) for total of 487.709300658000 dcy

stealth address amount amount idx
00: e8cbda200242c23546e090c4a7cb6a59ba613310ebf6b78912854cf6eb9efa4a 487.709300658000 49748 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": 30142, "vin": [ { "gen": { "height": 30132 } } ], "vout": [ { "amount": 487709300658, "target": { "key": "e8cbda200242c23546e090c4a7cb6a59ba613310ebf6b78912854cf6eb9efa4a" } } ], "extra": [ 1, 249, 45, 221, 202, 236, 112, 184, 238, 80, 26, 130, 186, 242, 210, 139, 158, 150, 50, 175, 126, 246, 174, 207, 133, 240, 222, 191, 242, 229, 98, 121, 232, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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