Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91a4f26595013aa6581278d854fe2e340efa6e622ffc0db526e7961f7ed43a7

Tx prefix hash: 78b8f04574d74c94e3f2bc94c02103b42e580868e8d678cf04d981c32a172730
Tx public key: b6aeed64aa1a9d2a93a7fc8f73a2740e77a63f763831eba6a60c69a64900b422
Timestamp: 1711131456 Timestamp [UCT]: 2024-03-22 18:17:36 Age [y:d:h:m:s]: 01:038:11:16:03
Block: 984050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288466 RingCT/type: yes/0
Extra: 01b6aeed64aa1a9d2a93a7fc8f73a2740e77a63f763831eba6a60c69a64900b42202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7031e80356568b9dcc38bc2008ee8554f6365092ed195ec8d8f48f7b0e398e8 0.600000000000 1444205 of 15

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": 984060, "vin": [ { "gen": { "height": 984050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7031e80356568b9dcc38bc2008ee8554f6365092ed195ec8d8f48f7b0e398e8" } } ], "extra": [ 1, 182, 174, 237, 100, 170, 26, 157, 42, 147, 167, 252, 143, 115, 162, 116, 14, 119, 166, 63, 118, 56, 49, 235, 166, 166, 12, 105, 166, 73, 0, 180, 34, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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