Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 828961e0bcc4fe3dfd9520bc44c2367c75be78aaceed73de77ed406fde101beb

Tx prefix hash: bc593d855f090f3f5e59ee19f778bf858af82831a50b3f6b88308815b1ba9e86
Tx public key: f82616c060da320c4ff6057fb84e6355259f3616548d063752f4f023a0f9eb8b
Timestamp: 1775109146 Timestamp [UTC]: 2026-04-02 05:52:26 Age [y:d:h:m:s]: 00:228:19:38:42
Block: 1511023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169027 RingCT/type: yes/0
Extra: 01f82616c060da320c4ff6057fb84e6355259f3616548d063752f4f023a0f9eb8b021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 75dc7dfaef53337bd73b886ed727470afccbc6c4bad8f483497341951cd90ab4 0.000600000000 2000811 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": 1511033, "vin": [ { "gen": { "height": 1511023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75dc7dfaef53337bd73b886ed727470afccbc6c4bad8f483497341951cd90ab4" } } ], "extra": [ 1, 248, 38, 22, 192, 96, 218, 50, 12, 79, 246, 5, 127, 184, 78, 99, 85, 37, 159, 54, 22, 84, 141, 6, 55, 82, 244, 240, 35, 160, 249, 235, 139, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: