Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 230cf1718937c1c3f83531bcf1ddcffe3e36601e7816f82dddcc45a956a26ee2

Tx prefix hash: 55e238116f034b886c4bf30732cfdb2706ec4b0351e9b6d61282fb27d20c283a
Tx public key: ae032acd47cf4d10a1fae3a03df6455223cc3fca72e727b3d9703761d2edbc1b
Timestamp: 1756127302 Timestamp [UTC]: 2025-08-25 13:08:22 Age [y:d:h:m:s]: 01:083:17:57:13
Block: 1354149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326068 RingCT/type: yes/0
Extra: 01ae032acd47cf4d10a1fae3a03df6455223cc3fca72e727b3d9703761d2edbc1b0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 552bfdf69498a6f381eb8cad59dc78d9242019aecad64bbd94c6a7310b9e79f1 0.000600000000 1842130 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": 1354159, "vin": [ { "gen": { "height": 1354149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552bfdf69498a6f381eb8cad59dc78d9242019aecad64bbd94c6a7310b9e79f1" } } ], "extra": [ 1, 174, 3, 42, 205, 71, 207, 77, 16, 161, 250, 227, 160, 61, 246, 69, 82, 35, 204, 63, 202, 114, 231, 39, 179, 217, 112, 55, 97, 210, 237, 188, 27, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: