Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bb7e1109d266826b07fa2f03126dd4c098435f222ba863b8dc40cfd356fc4c

Tx prefix hash: d6f1b2a55578958af3d784917dbac314af089bc2931a4124cd054f6d68741a75
Tx public key: 3bd5c6354973732bcc23592593bd0eefaf1b5bb008ce4ebba7b3367ae896b8c1
Timestamp: 1774231771 Timestamp [UTC]: 2026-03-23 02:09:31 Age [y:d:h:m:s]: 00:238:08:26:10
Block: 1503754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175836 RingCT/type: yes/0
Extra: 013bd5c6354973732bcc23592593bd0eefaf1b5bb008ce4ebba7b3367ae896b8c1021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3cd37825f519af319aaefc0131e311f7f95906295a80d80b555cd51f0be23b88 0.000600000000 1993466 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": 1503764, "vin": [ { "gen": { "height": 1503754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd37825f519af319aaefc0131e311f7f95906295a80d80b555cd51f0be23b88" } } ], "extra": [ 1, 59, 213, 198, 53, 73, 115, 115, 43, 204, 35, 89, 37, 147, 189, 14, 239, 175, 27, 91, 176, 8, 206, 78, 187, 167, 179, 54, 122, 232, 150, 184, 193, 2, 17, 0, 0, 0, 4, 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: