Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7812319b7b87c0d3ff7edda62c82945172a3799ea0b678eb0568e11cf5e8136d

Tx prefix hash: bd650d634a3e00df854db37142970ef7f3d329919b7585b58739145f09d194d9
Tx public key: f43548de8e3115009e258c2785d4dd181f35f02c31f47864ef154aeb7a64e796
Timestamp: 1772688481 Timestamp [UTC]: 2026-03-05 05:28:01 Age [y:d:h:m:s]: 00:261:14:50:06
Block: 1491010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192484 RingCT/type: yes/0
Extra: 01f43548de8e3115009e258c2785d4dd181f35f02c31f47864ef154aeb7a64e796021100000002da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a9bb93aca0e9a1edeac3f41f436621ef72acde1e4f27fccaa524bdc7df3011e2 0.000600000000 1980524 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": 1491020, "vin": [ { "gen": { "height": 1491010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9bb93aca0e9a1edeac3f41f436621ef72acde1e4f27fccaa524bdc7df3011e2" } } ], "extra": [ 1, 244, 53, 72, 222, 142, 49, 21, 0, 158, 37, 140, 39, 133, 212, 221, 24, 31, 53, 240, 44, 49, 244, 120, 100, 239, 21, 74, 235, 122, 100, 231, 150, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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: