Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 847a9bdc40e60cec45135c5736d110ec09b3b7f5660ce87ee6ec8e7dc65e1c1a

Tx prefix hash: 1dc7251e7ef7acdf309125f085e0149a991d7be40cbb1e0f7b855a8b02ba2d34
Tx public key: 85b42bba5bf1e8b879400442ed3dcdb5987ae26f580bb8d58e0665cd2bd75bf9
Timestamp: 1584518213 Timestamp [UCT]: 2020-03-18 07:56:53 Age [y:d:h:m:s]: 04:337:17:49:59
Block: 84797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136793 RingCT/type: yes/0
Extra: 0185b42bba5bf1e8b879400442ed3dcdb5987ae26f580bb8d58e0665cd2bd75bf902110000000b8a2ee0d9000000000000000000

1 output(s) for total of 321.406713441000 dcy

stealth address amount amount idx
00: b7439caf9c01a112a447acd926f761c09775045476fa246661fd8b5229bc78b6 321.406713441000 153523 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": 84807, "vin": [ { "gen": { "height": 84797 } } ], "vout": [ { "amount": 321406713441, "target": { "key": "b7439caf9c01a112a447acd926f761c09775045476fa246661fd8b5229bc78b6" } } ], "extra": [ 1, 133, 180, 43, 186, 91, 241, 232, 184, 121, 64, 4, 66, 237, 61, 205, 181, 152, 122, 226, 111, 88, 11, 184, 213, 142, 6, 101, 205, 43, 215, 91, 249, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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