Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d319d32926a2d763d1972500fdcbe27959b2651ff76407d8b081a51f1de91613

Tx prefix hash: 648748a7f5a40e7e2905f2995c47b5cf6a78dc4cd5f559adc5d47b2c532fbc7d
Tx public key: e9a3975aa6ef79654fd93f87903c968134b03961419447ccd8b9fc16ef54b36f
Timestamp: 1574555370 Timestamp [UCT]: 2019-11-24 00:29:30 Age [y:d:h:m:s]: 05:073:17:49:23
Block: 16034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1195337 RingCT/type: yes/0
Extra: 01e9a3975aa6ef79654fd93f87903c968134b03961419447ccd8b9fc16ef54b36f021100000001d50ca400000000000000000000

1 output(s) for total of 543.092224008000 dcy

stealth address amount amount idx
00: ea6588085c66d93af30dbb835804ec279e8135bc723ad78e42427bec5111847f 543.092224008000 22095 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": 16044, "vin": [ { "gen": { "height": 16034 } } ], "vout": [ { "amount": 543092224008, "target": { "key": "ea6588085c66d93af30dbb835804ec279e8135bc723ad78e42427bec5111847f" } } ], "extra": [ 1, 233, 163, 151, 90, 166, 239, 121, 101, 79, 217, 63, 135, 144, 60, 150, 129, 52, 176, 57, 97, 65, 148, 71, 204, 216, 185, 252, 22, 239, 84, 179, 111, 2, 17, 0, 0, 0, 1, 213, 12, 164, 0, 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