Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c6dbd880451753a21a028322a824c5379f927764954852ef750a3c74fcbc1d

Tx prefix hash: 1306f14f8c655733b56e639dd2f2c0cc6c5d701a02e34e3ac418a79af8ad4d04
Tx public key: be2268ab3fb5dc9787e7a13de7b161e191e06891ebc930be6a42ba1724c4900d
Timestamp: 1722317542 Timestamp [UCT]: 2024-07-30 05:32:22 Age [y:d:h:m:s]: 00:239:04:51:23
Block: 1076770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170840 RingCT/type: yes/0
Extra: 01be2268ab3fb5dc9787e7a13de7b161e191e06891ebc930be6a42ba1724c4900d02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86dd41d4ee1ca43f5e94ac5619170e064c2373b316bb895ff2916ff071ab7a4d 0.600000000000 1549311 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": 1076780, "vin": [ { "gen": { "height": 1076770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86dd41d4ee1ca43f5e94ac5619170e064c2373b316bb895ff2916ff071ab7a4d" } } ], "extra": [ 1, 190, 34, 104, 171, 63, 181, 220, 151, 135, 231, 161, 61, 231, 177, 97, 225, 145, 224, 104, 145, 235, 201, 48, 190, 106, 66, 186, 23, 36, 196, 144, 13, 2, 17, 0, 0, 0, 9, 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