Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 369f837765d4e18d99f1e8a85e807988dca27821b99f45d8a82786d49eb051aa

Tx prefix hash: dcd138e201dc72b20f428094738db0cc3ab50b45d8b32484719875090fb05a41
Tx public key: 2bc9f39810b2afa80585e65c6f14a7dfb145a90315b4f6479b6079e2caf3a495
Timestamp: 1759314141 Timestamp [UTC]: 2025-10-01 10:22:21 Age [y:d:h:m:s]: 01:044:01:08:32
Block: 1380366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297746 RingCT/type: yes/0
Extra: 012bc9f39810b2afa80585e65c6f14a7dfb145a90315b4f6479b6079e2caf3a495021100000008d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f48b2ef3c09855055da76b306cfef69c56f0ee6ce3a2d1c8e929e1d5f4b98953 0.000600000000 1868477 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": 1380376, "vin": [ { "gen": { "height": 1380366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f48b2ef3c09855055da76b306cfef69c56f0ee6ce3a2d1c8e929e1d5f4b98953" } } ], "extra": [ 1, 43, 201, 243, 152, 16, 178, 175, 168, 5, 133, 230, 92, 111, 20, 167, 223, 177, 69, 169, 3, 21, 180, 246, 71, 155, 96, 121, 226, 202, 243, 164, 149, 2, 17, 0, 0, 0, 8, 216, 231, 210, 65, 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: