Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a829cfe10cd56b6c4490c24573ee479b4e6e131abcf1eac456215f48a0625b7e

Tx prefix hash: 904f54667abfbf07f0645afba2bee54a2ca60485ce4ce9dd1aad2a8e65e3433d
Tx public key: 13142631320c729adbbc43394df2273f01b2adf408ef2954fa71de9b3e03eb3e
Timestamp: 1770404988 Timestamp [UTC]: 2026-02-06 19:09:48 Age [y:d:h:m:s]: 00:095:20:44:03
Block: 1472123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 60826 RingCT/type: yes/0
Extra: 0113142631320c729adbbc43394df2273f01b2adf408ef2954fa71de9b3e03eb3e020845704517839ae921

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61c64e0a6ab50f66fc8b0d50bca36e35a26e7c9e7ff7d4850d612835e56be1a3 0.000600000000 1961401 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": 1472133, "vin": [ { "gen": { "height": 1472123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c64e0a6ab50f66fc8b0d50bca36e35a26e7c9e7ff7d4850d612835e56be1a3" } } ], "extra": [ 1, 19, 20, 38, 49, 50, 12, 114, 154, 219, 188, 67, 57, 77, 242, 39, 63, 1, 178, 173, 244, 8, 239, 41, 84, 250, 113, 222, 155, 62, 3, 235, 62, 2, 8, 69, 112, 69, 23, 131, 154, 233, 33 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: