Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a717efef6d86818974ff602cf04c8a080d34fee26935f05e4f0d18775e19f1ca

Tx prefix hash: f75c90dd2ea0d22867c03435e62aff1f6c65bd2dd3f7558e6e559d057a066aca
Tx public key: bd97adc84c73fa1fa3b6cb655cf746db8651feede71379ffc41f1c2559c6fd4d
Timestamp: 1775059416 Timestamp [UTC]: 2026-04-01 16:03:36 Age [y:d:h:m:s]: 00:232:04:21:41
Block: 1510613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171525 RingCT/type: yes/0
Extra: 01bd97adc84c73fa1fa3b6cb655cf746db8651feede71379ffc41f1c2559c6fd4d021100000003e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c1c873f28cefd22f2e5312b537baba995d1f0d4bfe0680b6a7c02bb23ab95d34 0.000600000000 2000399 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": 1510623, "vin": [ { "gen": { "height": 1510613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c873f28cefd22f2e5312b537baba995d1f0d4bfe0680b6a7c02bb23ab95d34" } } ], "extra": [ 1, 189, 151, 173, 200, 76, 115, 250, 31, 163, 182, 203, 101, 92, 247, 70, 219, 134, 81, 254, 237, 231, 19, 121, 255, 196, 31, 28, 37, 89, 198, 253, 77, 2, 17, 0, 0, 0, 3, 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: