Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03bbebf972e0cf959d3a54e3dd0bcdc8e4085033e5cd5596ad6f5c3bf9fdf625

Tx prefix hash: e69127728a944c68e8f37c6862ea4ab90882ce1f429ed97fedaa7f130046e00f
Tx public key: 57dbb878455488b0509c141c0dbff4f0b710cbda93e523d99e62f307fe52140e
Timestamp: 1775090108 Timestamp [UTC]: 2026-04-02 00:35:08 Age [y:d:h:m:s]: 00:226:23:33:15
Block: 1510858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167643 RingCT/type: yes/0
Extra: 0157dbb878455488b0509c141c0dbff4f0b710cbda93e523d99e62f307fe52140e021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2b5d73978145aa58aa09a7031ef1e040b01004ebd7f8ba1149622f9028f959f7 0.000600000000 2000644 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": 1510868, "vin": [ { "gen": { "height": 1510858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b5d73978145aa58aa09a7031ef1e040b01004ebd7f8ba1149622f9028f959f7" } } ], "extra": [ 1, 87, 219, 184, 120, 69, 84, 136, 176, 80, 156, 20, 28, 13, 191, 244, 240, 183, 16, 203, 218, 147, 229, 35, 217, 158, 98, 243, 7, 254, 82, 20, 14, 2, 17, 0, 0, 0, 1, 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: