Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4be14ab0dbdd1de69b1eb0c6209ec3b484e150f0cda1b254b7e71adbc1d0ff

Tx prefix hash: b23b4281f73ed04efe32ea198561022da7d9f81a01f3f3f8dc295fff584e23e5
Tx public key: bd614ae87227c41b364cf45b90f91f92503fa42a2fd28cbd9cc52c72419d1a13
Timestamp: 1760654008 Timestamp [UTC]: 2025-10-16 22:33:28 Age [y:d:h:m:s]: 01:032:02:23:07
Block: 1391489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289277 RingCT/type: yes/0
Extra: 01bd614ae87227c41b364cf45b90f91f92503fa42a2fd28cbd9cc52c72419d1a130211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 93b730b27258087c84067b27d78817f41c33d1891a45b6202f1e2f588f9ba150 0.000600000000 1879736 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": 1391499, "vin": [ { "gen": { "height": 1391489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93b730b27258087c84067b27d78817f41c33d1891a45b6202f1e2f588f9ba150" } } ], "extra": [ 1, 189, 97, 74, 232, 114, 39, 196, 27, 54, 76, 244, 91, 144, 249, 31, 146, 80, 63, 164, 42, 47, 210, 140, 189, 156, 197, 44, 114, 65, 157, 26, 19, 2, 17, 0, 0, 0, 2, 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: