Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0346f533487d47255f50fa2943bace639b34ebd2feb405fd7e28d19f6f82feda

Tx prefix hash: a76612984d244df7da1d82dc52b3789d7370fd7b91506155a92b669508b1ce5f
Tx public key: fa3c17b9fc16d2b4d2ea8d42c45b24d401754957ef972dbf0715e5644ee303c5
Timestamp: 1742073660 Timestamp [UTC]: 2025-03-15 21:21:00 Age [y:d:h:m:s]: 01:057:21:10:39
Block: 1240102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292187 RingCT/type: yes/0
Extra: 01fa3c17b9fc16d2b4d2ea8d42c45b24d401754957ef972dbf0715e5644ee303c50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e09172520355a665ce893067cb0eb8ad23b47d7b260409f6de93fbfd2e1f7d37 0.000600000000 1727067 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": 1240112, "vin": [ { "gen": { "height": 1240102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e09172520355a665ce893067cb0eb8ad23b47d7b260409f6de93fbfd2e1f7d37" } } ], "extra": [ 1, 250, 60, 23, 185, 252, 22, 210, 180, 210, 234, 141, 66, 196, 91, 36, 212, 1, 117, 73, 87, 239, 151, 45, 191, 7, 21, 229, 100, 78, 227, 3, 197, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: