Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bdb366361d68a31f76fde28fdcd620fd0b3c4219fda4473fdd1cf5eb3d6b8ff

Tx prefix hash: d654010e99fff30a3679b4dbe62accf2f13703887cd36bc5a1a54af03f7a87c1
Tx public key: 6ab9e3128cc9442dacc29ab0a23c22d9635835cd0f72aa0f760ef70706b654d0
Timestamp: 1749399366 Timestamp [UTC]: 2025-06-08 16:16:06 Age [y:d:h:m:s]: 01:160:13:25:36
Block: 1300740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378696 RingCT/type: yes/0
Extra: 016ab9e3128cc9442dacc29ab0a23c22d9635835cd0f72aa0f760ef70706b654d002110000000243846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c14362dd4f29d52785de7e1f5cb9653e2923304afef032c7e2b7afcc635a851 0.000600000000 1788289 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": 1300750, "vin": [ { "gen": { "height": 1300740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c14362dd4f29d52785de7e1f5cb9653e2923304afef032c7e2b7afcc635a851" } } ], "extra": [ 1, 106, 185, 227, 18, 140, 201, 68, 45, 172, 194, 154, 176, 162, 60, 34, 217, 99, 88, 53, 205, 15, 114, 170, 15, 118, 14, 247, 7, 6, 182, 84, 208, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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: