Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784694f250fba3f9fa9b48cec617e8dfecf3f8ff8e8189b5e9890b57e995e077

Tx prefix hash: 7bfd401c3eb9f8a99517c634ea4fb7d2f56139e902a9ebb94ee951ad381c6ff2
Tx public key: 70c1349017b1a71d5920e9b6e060053fba5e2bc766753b6856b364774e311953
Timestamp: 1745966068 Timestamp [UTC]: 2025-04-29 22:34:28 Age [y:d:h:m:s]: 01:203:21:20:27
Block: 1272307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409808 RingCT/type: yes/0
Extra: 0170c1349017b1a71d5920e9b6e060053fba5e2bc766753b6856b364774e3119530211000000099f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 48921d55dd181cf41f1dc734d3f2fc265b3aa52ca4b55883c3dc6051c818e53d 0.000600000000 1759580 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": 1272317, "vin": [ { "gen": { "height": 1272307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48921d55dd181cf41f1dc734d3f2fc265b3aa52ca4b55883c3dc6051c818e53d" } } ], "extra": [ 1, 112, 193, 52, 144, 23, 177, 167, 29, 89, 32, 233, 182, 224, 96, 5, 63, 186, 94, 43, 199, 102, 117, 59, 104, 86, 179, 100, 119, 78, 49, 25, 83, 2, 17, 0, 0, 0, 9, 159, 159, 230, 140, 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: