Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd49e511cc26e994c6448efcb0e1c206a863799778f21b3cbabca4a034dc6593

Tx prefix hash: cee9bc07a8f40b3158059e588995e174fda7528c5381d3343fe580eb35a4b4e6
Tx public key: 54137566b5cdf6522a2960ee3997575afec575722fb8d4be9d99ef7e184af5ae
Timestamp: 1574424547 Timestamp [UCT]: 2019-11-22 12:09:07 Age [y:d:h:m:s]: 05:038:01:27:58
Block: 14415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1170619 RingCT/type: yes/0
Extra: 0154137566b5cdf6522a2960ee3997575afec575722fb8d4be9d99ef7e184af5ae021100000001354bbe3b000000000000000000

1 output(s) for total of 549.842120847000 dcy

stealth address amount amount idx
00: 3adbec6923bacda019fb9f1c970e194beeac64fb30f181d43766c1d3d9000e9e 549.842120847000 18241 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": 14425, "vin": [ { "gen": { "height": 14415 } } ], "vout": [ { "amount": 549842120847, "target": { "key": "3adbec6923bacda019fb9f1c970e194beeac64fb30f181d43766c1d3d9000e9e" } } ], "extra": [ 1, 84, 19, 117, 102, 181, 205, 246, 82, 42, 41, 96, 238, 57, 151, 87, 90, 254, 197, 117, 114, 47, 184, 212, 190, 157, 153, 239, 126, 24, 74, 245, 174, 2, 17, 0, 0, 0, 1, 53, 75, 190, 59, 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