Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00545ab363ba4c5b2bfc7bb426c3f80fbd62848786f701eac7fd8013ca1963d1

Tx prefix hash: 8ab3c0f7b1bb0bacadcb3d8a0391f08a8c8803d77a3aadba0761865587a65a03
Tx public key: f10ef84523db0a6450f5064ba914b4ac371e8a8bc5ab8e9fe99a44e583e2d6a0
Timestamp: 1774653345 Timestamp [UTC]: 2026-03-27 23:15:45 Age [y:d:h:m:s]: 00:235:05:25:44
Block: 1507255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173634 RingCT/type: yes/0
Extra: 01f10ef84523db0a6450f5064ba914b4ac371e8a8bc5ab8e9fe99a44e583e2d6a002110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 42b09bdacffe716362c3e14dd60f3b73e2b71b78a5fb5b986887c372ac3f1a35 0.000600000000 1997007 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 dinastycoin-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": 1507265, "vin": [ { "gen": { "height": 1507255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b09bdacffe716362c3e14dd60f3b73e2b71b78a5fb5b986887c372ac3f1a35" } } ], "extra": [ 1, 241, 14, 248, 69, 35, 219, 10, 100, 80, 245, 6, 75, 169, 20, 180, 172, 55, 30, 138, 139, 197, 171, 142, 159, 233, 154, 68, 229, 131, 226, 214, 160, 2, 17, 0, 0, 0, 12, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: