Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 114e4dab1c06c2b019ba95580f83d4cdd8cb1adc2f06389cd77a69fa133763a7

Tx prefix hash: dd653abb0ae338f92ef0c6f77615d1e5e7efca872b0b2601e56ee1a8475e88dc
Tx public key: 502633b5937f31269f814b4046a57ad05930b2412a05b2f6e84466a57f9dae7a
Timestamp: 1698509054 Timestamp [UCT]: 2023-10-28 16:04:14 Age [y:d:h:m:s]: 01:124:07:10:44
Block: 879599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349802 RingCT/type: yes/0
Extra: 01502633b5937f31269f814b4046a57ad05930b2412a05b2f6e84466a57f9dae7a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.747348879000 dcy

stealth address amount amount idx
00: 4294a66c4442a3caedf964eced137b4ca34d69619ea8f119dd2c8d8531d5d570 0.747348879000 1335133 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": 879609, "vin": [ { "gen": { "height": 879599 } } ], "vout": [ { "amount": 747348879, "target": { "key": "4294a66c4442a3caedf964eced137b4ca34d69619ea8f119dd2c8d8531d5d570" } } ], "extra": [ 1, 80, 38, 51, 181, 147, 127, 49, 38, 159, 129, 75, 64, 70, 165, 122, 208, 89, 48, 178, 65, 42, 5, 178, 246, 232, 68, 102, 165, 127, 157, 174, 122, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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