Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da2918b52a7b183a82d1c5448c1bf6f7a4c169a80f29343793408b7c7d2e2dc

Tx prefix hash: aa6a17975ab701356172c892d145c947bae41a873d2f92728339e36dde9edfa6
Tx public key: 6bfc718d3f2b42a4d801d01048885c504dc4b496df991976103ed14348e5f69a
Timestamp: 1728894975 Timestamp [UTC]: 2024-10-14 08:36:15 Age [y:d:h:m:s]: 02:038:07:15:49
Block: 1131307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552187 RingCT/type: yes/0
Extra: 016bfc718d3f2b42a4d801d01048885c504dc4b496df991976103ed14348e5f69a021100000002e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1b95e1a0032d51bff859aa585d330f85a5cc84c9069fd235c523afaf754b24e 0.000600000000 1614196 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": 1131317, "vin": [ { "gen": { "height": 1131307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b95e1a0032d51bff859aa585d330f85a5cc84c9069fd235c523afaf754b24e" } } ], "extra": [ 1, 107, 252, 113, 141, 63, 43, 66, 164, 216, 1, 208, 16, 72, 136, 92, 80, 77, 196, 180, 150, 223, 153, 25, 118, 16, 62, 209, 67, 72, 229, 246, 154, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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: