Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8aa062b36f560d6dde48dc1187ad40b99ef3a2da8a4d2155e33ff287380d5f1

Tx prefix hash: 5490e5ab4aaf5dfd3808fc75b4a268b969daf32a4018d464ab3bf6cac9ef2d05
Tx public key: 68a029f7e5d4b919d791ec5a2126f4e20d72f7f63683df38ed070509680d13cb
Timestamp: 1772412676 Timestamp [UTC]: 2026-03-02 00:51:16 Age [y:d:h:m:s]: 00:246:16:00:25
Block: 1488712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180768 RingCT/type: yes/0
Extra: 0168a029f7e5d4b919d791ec5a2126f4e20d72f7f63683df38ed070509680d13cb021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f47a2ec4437d4bec84356d273ac73f92a1a878f6048a1eb244e43af5ebc65f73 0.000600000000 1978192 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": 1488722, "vin": [ { "gen": { "height": 1488712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f47a2ec4437d4bec84356d273ac73f92a1a878f6048a1eb244e43af5ebc65f73" } } ], "extra": [ 1, 104, 160, 41, 247, 229, 212, 185, 25, 215, 145, 236, 90, 33, 38, 244, 226, 13, 114, 247, 246, 54, 131, 223, 56, 237, 7, 5, 9, 104, 13, 19, 203, 2, 17, 0, 0, 0, 4, 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: