Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7f64ed030d8977cb3d7cfdcb403b04d2f0b1a84b93e689da4c3e5f4c3bf55b

Tx prefix hash: aa193595c38ca5ac6d1f29a9681025c559fc9faf8aab35f73a56fae7e40589dd
Tx public key: 6abc86f12e02a4bf5261854ee41dcc1193c327f84c67c9e9244c2b8d0c7f712d
Timestamp: 1790528822 Timestamp [UTC]: 2026-09-27 17:07:02 Age [y:d:h:m:s]: 00:046:23:58:51
Block: 1644850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 32685 RingCT/type: yes/0
Extra: 016abc86f12e02a4bf5261854ee41dcc1193c327f84c67c9e9244c2b8d0c7f712d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5fb9f71b14e1b5299a60ab7a8119dc1ac2ca50d825e98bfaa157c02e538b5775 0.000600000000 2134936 of 15 <7a>

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": 1644860, "vin": [ { "gen": { "height": 1644850 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "5fb9f71b14e1b5299a60ab7a8119dc1ac2ca50d825e98bfaa157c02e538b5775", "view_tag": "7a" } } } ], "extra": [ 1, 106, 188, 134, 241, 46, 2, 164, 191, 82, 97, 133, 78, 228, 29, 204, 17, 147, 195, 39, 248, 76, 103, 201, 233, 36, 76, 43, 141, 12, 127, 113, 45 ], "rct_signatures": { "type": 0 } }


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