Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4ea8ea716063d74e7334470c8cfca9aa90226f42b1d1474babd89f5678f3df

Tx prefix hash: 86376ea3c3c7f16b29fba9f5328ee3bde07afce3ea008fe929630b14599211ec
Tx public key: c5479e0ea6513e2990d9684b3786debe86a1b0d13bc0b37c4657efe541e9eef5
Timestamp: 1774763863 Timestamp [UTC]: 2026-03-29 05:57:43 Age [y:d:h:m:s]: 00:234:09:23:55
Block: 1508167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173043 RingCT/type: yes/0
Extra: 01c5479e0ea6513e2990d9684b3786debe86a1b0d13bc0b37c4657efe541e9eef5021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a3aad9eda21eab11d167a733cb0c9ef72ca726b8443638ba24c48e6824ec51f 0.000600000000 1997919 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": 1508177, "vin": [ { "gen": { "height": 1508167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a3aad9eda21eab11d167a733cb0c9ef72ca726b8443638ba24c48e6824ec51f" } } ], "extra": [ 1, 197, 71, 158, 14, 166, 81, 62, 41, 144, 217, 104, 75, 55, 134, 222, 190, 134, 161, 176, 209, 59, 192, 179, 124, 70, 87, 239, 229, 65, 233, 238, 245, 2, 17, 0, 0, 0, 1, 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: