Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212d35fb50d140c6b9fcf4be46cc7665f8933cb7fd1d3dd38afa95d304f9bde2

Tx prefix hash: 7dd466beeaa7c6dcb8e112b8e537a1126c1375789dda4a305d2cefc4f1157eb2
Tx public key: 46a1194523452c44b5874352d501f85285219511ff6e69c94dad5a72d36b339e
Timestamp: 1771836764 Timestamp [UTC]: 2026-02-23 08:52:44 Age [y:d:h:m:s]: 00:264:11:36:39
Block: 1483958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194421 RingCT/type: yes/0
Extra: 0146a1194523452c44b5874352d501f85285219511ff6e69c94dad5a72d36b339e02110000000be4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a10d7b65c1981b30de508b619d21b27fc2d6a12e26fc4f2bc3d8b3e47b5feab1 0.000600000000 1973372 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": 1483968, "vin": [ { "gen": { "height": 1483958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a10d7b65c1981b30de508b619d21b27fc2d6a12e26fc4f2bc3d8b3e47b5feab1" } } ], "extra": [ 1, 70, 161, 25, 69, 35, 69, 44, 68, 181, 135, 67, 82, 213, 1, 248, 82, 133, 33, 149, 17, 255, 110, 105, 201, 77, 173, 90, 114, 211, 107, 51, 158, 2, 17, 0, 0, 0, 11, 228, 245, 25, 63, 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: