Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ece6a4458d9a8cb52a226ecb6a926db9637301b4b79d3e54f4ca76d02293412

Tx prefix hash: 7066b1018e5060711efc4c06c2e439a440e07769ed2e51ed339e3425a6e0d8d2
Tx public key: 358940566db1474ae9fff96f5e7cc944a3f8be432d77e98db4bc439358fd0e6d
Timestamp: 1745996337 Timestamp [UCT]: 2025-04-30 06:58:57 Age [y:d:h:m:s]: 00:235:21:11:48
Block: 1272571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166330 RingCT/type: yes/0
Extra: 01358940566db1474ae9fff96f5e7cc944a3f8be432d77e98db4bc439358fd0e6d0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9f00b542a8ec8e39e6947632eaf76a9bcc7ddfc04b86c4bf280b6117ba85442 0.600000000000 1759846 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": 1272581, "vin": [ { "gen": { "height": 1272571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9f00b542a8ec8e39e6947632eaf76a9bcc7ddfc04b86c4bf280b6117ba85442" } } ], "extra": [ 1, 53, 137, 64, 86, 109, 177, 71, 74, 233, 255, 249, 111, 94, 124, 201, 68, 163, 248, 190, 67, 45, 119, 233, 141, 180, 188, 67, 147, 88, 253, 14, 109, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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