Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7658a8fdf60d0f4049afda76f11e427555ddbfa82e45a0bd8dc56ddcdd59b1f8

Tx prefix hash: f6d51c281e2f383bd62d5fedec857fac2d70439717a7f0f52dcde2dbd62f909d
Tx public key: 3f9d0424630369839c7247fe4bfa1070910fe9937128c49d359922b4196538c5
Timestamp: 1675035053 Timestamp [UCT]: 2023-01-29 23:30:53 Age [y:d:h:m:s]: 02:069:18:54:01
Block: 685665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571490 RingCT/type: yes/0
Extra: 013f9d0424630369839c7247fe4bfa1070910fe9937128c49d359922b4196538c5021100000002835e4d22000000000000000000

1 output(s) for total of 3.281762561000 dcy

stealth address amount amount idx
00: 6a17a1494855aa9bf65aa5731613fc83e3e3e51e96f07c085c189916b7e957d5 3.281762561000 1128030 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": 685675, "vin": [ { "gen": { "height": 685665 } } ], "vout": [ { "amount": 3281762561, "target": { "key": "6a17a1494855aa9bf65aa5731613fc83e3e3e51e96f07c085c189916b7e957d5" } } ], "extra": [ 1, 63, 157, 4, 36, 99, 3, 105, 131, 156, 114, 71, 254, 75, 250, 16, 112, 145, 15, 233, 147, 113, 40, 196, 157, 53, 153, 34, 180, 25, 101, 56, 197, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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