Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56d094d73819a9e75f7e449b2c533bf48dbb432f2a2ae91c8d4a4ef7db953df4

Tx prefix hash: 354ad39511d85c5ac0dfff984078b243b8eeaa008ff99f7b40a54992b103f73f
Tx public key: eec390447191b514fa2d414543d76b8ca02ae06267f06262db1a25a7e26e3d19
Timestamp: 1765038049 Timestamp [UTC]: 2025-12-06 16:20:49 Age [y:d:h:m:s]: 00:348:18:24:41
Block: 1427815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254813 RingCT/type: yes/0
Extra: 01eec390447191b514fa2d414543d76b8ca02ae06267f06262db1a25a7e26e3d1902110000000270609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 76217dd03661a0f9a79cc3b79ceff20cce3e58c04c42cb2e628337bfe9077981 0.000600000000 1916522 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": 1427825, "vin": [ { "gen": { "height": 1427815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76217dd03661a0f9a79cc3b79ceff20cce3e58c04c42cb2e628337bfe9077981" } } ], "extra": [ 1, 238, 195, 144, 68, 113, 145, 181, 20, 250, 45, 65, 69, 67, 215, 107, 140, 160, 42, 224, 98, 103, 240, 98, 98, 219, 26, 37, 167, 226, 110, 61, 25, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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: