Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d391230f396510a2fa4aa87cabdd4e864b9310574f37dbacb9e99392b1c2c179

Tx prefix hash: d9adb5de0ac58f78b4a1bf618ba3197b6abfb825f306733277735ee66db4769c
Tx public key: 9732fe9de7c7bbb286c12b7e670fa6e9352b77db4ece2f9cb7ea562d31e52a98
Timestamp: 1772980111 Timestamp [UTC]: 2026-03-08 14:28:31 Age [y:d:h:m:s]: 00:258:23:33:34
Block: 1493428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190066 RingCT/type: yes/0
Extra: 019732fe9de7c7bbb286c12b7e670fa6e9352b77db4ece2f9cb7ea562d31e52a9802110000000ff188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16b8eb3d3a4edc137498dc2241ede5e62f9d6aa25e0431349fab81f0dbc411ee 0.000600000000 1982988 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": 1493438, "vin": [ { "gen": { "height": 1493428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16b8eb3d3a4edc137498dc2241ede5e62f9d6aa25e0431349fab81f0dbc411ee" } } ], "extra": [ 1, 151, 50, 254, 157, 231, 199, 187, 178, 134, 193, 43, 126, 103, 15, 166, 233, 53, 43, 119, 219, 78, 206, 47, 156, 183, 234, 86, 45, 49, 229, 42, 152, 2, 17, 0, 0, 0, 15, 241, 136, 200, 168, 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: