Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35577ff3aa99964f5f2b9f95f771ed1558d1be4bf32c0637aa84f2c04a794a4e

Tx prefix hash: e10934d66f460ce9a9f8ff69bb39bf8e02990ecaa7e07ca95b059296987b79c3
Tx public key: 2525e3f0f9933449f97d68fab96bb9092e77e2962fb7ac42ee676beb8af03f6e
Timestamp: 1706650843 Timestamp [UCT]: 2024-01-30 21:40:43 Age [y:d:h:m:s]: 01:280:19:28:48
Block: 946867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459472 RingCT/type: yes/0
Extra: 012525e3f0f9933449f97d68fab96bb9092e77e2962fb7ac42ee676beb8af03f6e02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc16bdaa20ac4725a21d825c150c33da8e4798d4bc5286ce9729c532f410eee7 0.600000000000 1405207 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": 946877, "vin": [ { "gen": { "height": 946867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc16bdaa20ac4725a21d825c150c33da8e4798d4bc5286ce9729c532f410eee7" } } ], "extra": [ 1, 37, 37, 227, 240, 249, 147, 52, 73, 249, 125, 104, 250, 185, 107, 185, 9, 46, 119, 226, 150, 47, 183, 172, 66, 238, 103, 107, 235, 138, 240, 63, 110, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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