Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a4c86fa8af7f04e2fe61189e6aa4243cd0d9e7802d5d4a0de90bd362fa2004

Tx prefix hash: 4b9b656859415395cb01939e79687fb327455d5268ef16807a6c511075f6065b
Tx public key: f423e39165521d7b5ad102d78a7d5cf84c419c98b92775309b9501f324160fdf
Timestamp: 1726078840 Timestamp [UCT]: 2024-09-11 18:20:40 Age [y:d:h:m:s]: 00:245:03:17:14
Block: 1107950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175066 RingCT/type: yes/0
Extra: 01f423e39165521d7b5ad102d78a7d5cf84c419c98b92775309b9501f324160fdf02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cb9fa912091265fab083a6a45a0e84e8b987c1403e1c79c13f642a105a0978b 0.600000000000 1585673 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": 1107960, "vin": [ { "gen": { "height": 1107950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cb9fa912091265fab083a6a45a0e84e8b987c1403e1c79c13f642a105a0978b" } } ], "extra": [ 1, 244, 35, 227, 145, 101, 82, 29, 123, 90, 209, 2, 215, 138, 125, 92, 248, 76, 65, 156, 152, 185, 39, 117, 48, 155, 149, 1, 243, 36, 22, 15, 223, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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