Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5bd40622c86d8ae5d8a766a4f7f0c8a3b4cd2b0924a0e6401fda01cc7351551

Tx prefix hash: 6d799231d364c2ae5354ad2f1c711a743c3ed2bd4eac8d48d4435700834edd64
Tx public key: 20d81ae1e672e8580ea37ca8c3ef822d3fafdf063b5811248a79817ea9eee5d0
Timestamp: 1773519153 Timestamp [UTC]: 2026-03-14 20:12:33 Age [y:d:h:m:s]: 00:245:03:04:00
Block: 1497887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180585 RingCT/type: yes/0
Extra: 0120d81ae1e672e8580ea37ca8c3ef822d3fafdf063b5811248a79817ea9eee5d002110000000be4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f0603ebac1cecc30c90d5ced28aa13022bc949a3014aaabfde4f85562c6c7dcd 0.000600000000 1987529 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": 1497897, "vin": [ { "gen": { "height": 1497887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0603ebac1cecc30c90d5ced28aa13022bc949a3014aaabfde4f85562c6c7dcd" } } ], "extra": [ 1, 32, 216, 26, 225, 230, 114, 232, 88, 14, 163, 124, 168, 195, 239, 130, 45, 63, 175, 223, 6, 59, 88, 17, 36, 138, 121, 129, 126, 169, 238, 229, 208, 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: