Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b1a04d086c7f5ea24ef94496a29741be522f63f2f4e250bdc2e32ed4758acc

Tx prefix hash: 2c40531015e1319aa6424c194e8f1d19d1c3da832c16c0fa8492c13e6a48ee90
Tx public key: 6ea481b9f231f226d98dc3a6543897824e6962b13da748f96da1d3336aee07fb
Timestamp: 1743864850 Timestamp [UTC]: 2025-04-05 14:54:10 Age [y:d:h:m:s]: 01:223:17:23:44
Block: 1254912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423850 RingCT/type: yes/0
Extra: 016ea481b9f231f226d98dc3a6543897824e6962b13da748f96da1d3336aee07fb0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 176866415f394781c9b5b26a750855d2b6b1799daca19f27ab1f9c22e88b0212 0.000600000000 1742005 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": 1254922, "vin": [ { "gen": { "height": 1254912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "176866415f394781c9b5b26a750855d2b6b1799daca19f27ab1f9c22e88b0212" } } ], "extra": [ 1, 110, 164, 129, 185, 242, 49, 242, 38, 217, 141, 195, 166, 84, 56, 151, 130, 78, 105, 98, 177, 61, 167, 72, 249, 109, 161, 211, 51, 106, 238, 7, 251, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: