Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae1f300e113dbf9b65d1bda22754410d4f1e258b1e7ebb5e7786950b8e0d5f4c

Tx prefix hash: 94f26119e0b85cc2b0853f91196395f2bd193412c0aba61fa9dcb58475433309
Tx public key: e1a73843b318909444c5dd7eb66205a22cb1b891e7b1ef7697bcb26d6087dd7d
Timestamp: 1763854354 Timestamp [UCT]: 2025-11-22 23:32:34 Age [y:d:h:m:s]: 00:030:10:51:29
Block: 1417997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21797 RingCT/type: yes/0
Extra: 01e1a73843b318909444c5dd7eb66205a22cb1b891e7b1ef7697bcb26d6087dd7d0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a272dd8f425e2c23641751d56c4d2325675a07c413fd780de24d858cbabb494f 0.600000000000 1906524 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": 1418007, "vin": [ { "gen": { "height": 1417997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a272dd8f425e2c23641751d56c4d2325675a07c413fd780de24d858cbabb494f" } } ], "extra": [ 1, 225, 167, 56, 67, 179, 24, 144, 148, 68, 197, 221, 126, 182, 98, 5, 162, 44, 177, 184, 145, 231, 177, 239, 118, 151, 188, 178, 109, 96, 135, 221, 125, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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