Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e0f2e5115b6957860a3a987daa0fe8685206eda137559a60e657d3eff2cd91

Tx prefix hash: 4f22a402dbef07a7bd3c0583eefab9fd351e224ff4937cf77d2c3b1da147ce82
Tx public key: b59cf46d721cf25910a704149d9787c69c825985bb50df41721cf78c21ec9a34
Timestamp: 1744164169 Timestamp [UTC]: 2025-04-09 02:02:49 Age [y:d:h:m:s]: 01:219:05:57:22
Block: 1257383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420614 RingCT/type: yes/0
Extra: 01b59cf46d721cf25910a704149d9787c69c825985bb50df41721cf78c21ec9a340211000000036c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b51f08633f96a13976f6ead1d0950074d7832db9c113b131f6a8589e5c042ecb 0.000600000000 1744504 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": 1257393, "vin": [ { "gen": { "height": 1257383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b51f08633f96a13976f6ead1d0950074d7832db9c113b131f6a8589e5c042ecb" } } ], "extra": [ 1, 181, 156, 244, 109, 114, 28, 242, 89, 16, 167, 4, 20, 157, 151, 135, 198, 156, 130, 89, 133, 187, 80, 223, 65, 114, 28, 247, 140, 33, 236, 154, 52, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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: