Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff5bfc9ea4a6afbcb5f309b903f03b484903e718b51706028129b83ccc32acaf

Tx prefix hash: 2b0ee31652a3df3ed7510f10a7c60a19637200ef20007e01674d2d4c2bc382d3
Tx public key: 1d87a9ed18120fb628378895ee36974477baa41d827d4788e61ef8c0da38266e
Timestamp: 1638431221 Timestamp [UCT]: 2021-12-02 07:47:01 Age [y:d:h:m:s]: 03:066:19:58:47
Block: 386661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826432 RingCT/type: yes/0
Extra: 011d87a9ed18120fb628378895ee36974477baa41d827d4788e61ef8c0da38266e02110000000fb494d89c000000000000000000

1 output(s) for total of 32.124173834000 dcy

stealth address amount amount idx
00: 3b8ec983cf9d75c927cd8a7801af661333cf6229270ea523a1e619021d4da8d5 32.124173834000 780032 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": 386671, "vin": [ { "gen": { "height": 386661 } } ], "vout": [ { "amount": 32124173834, "target": { "key": "3b8ec983cf9d75c927cd8a7801af661333cf6229270ea523a1e619021d4da8d5" } } ], "extra": [ 1, 29, 135, 169, 237, 24, 18, 15, 182, 40, 55, 136, 149, 238, 54, 151, 68, 119, 186, 164, 29, 130, 125, 71, 136, 230, 30, 248, 192, 218, 56, 38, 110, 2, 17, 0, 0, 0, 15, 180, 148, 216, 156, 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